Side navigation
#7338 closed enhancement (duplicate)
Opened October 28, 2010 03:28AM UTC
Closed April 17, 2011 05:41AM UTC
Last modified April 17, 2011 05:41AM UTC
remove() with lots of elements inside has gotten significantly slower across all browsers in 1.4.3- very bad in IE 8
| Reported by: | brad@assistly.com | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | manipulation | Version: | 1.4.3 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Starting with jQuery 1.4.3 I have noticed that .remove() on IE8 has become very slow. Its also slower than 1.4.2 on other browsers but isn't as noticeable.
I have created a test in jsfiddle that adds 10,000 divs and then removes the parent using 1.4.2 and 1.4.3.
On a Quad Core PC (8GB Ram) with IE8 I see if taking 111ms using 1.4.2 and 200ms using 1.4.3.
Attachments (0)
Change History (8)
Changed October 29, 2010 05:32AM UTC by comment:1
| component: | unfiled → manipulation |
|---|---|
| priority: | undecided → low |
| status: | new → open |
| type: | bug → enhancement |
Changed October 31, 2010 01:55AM UTC by comment:2
So I'm a little confused how this is a feature when it regressed from 1.4.2 to 1.4.3. Its very noticeable in our app and we have had to rollback to 1.4.2 due to user complaints
Changed November 04, 2010 02:12AM UTC by comment:3
Any chance of consideration for 1.4.4? This is impacting performance in our application.
Changed February 16, 2011 02:22AM UTC by comment:4
This also effects our site to the point of causing the "scripts on this page are taking too long warning". What is the status? This has caused a lot of errors and errors in 1.4.2 cant be addressed (the error about unload = undefined) which is fixed in the newer versions.
Changed February 16, 2011 02:28AM UTC by comment:5
THis is the code that takes a long time:
$("#SubReportNodeToReplace").empty().html(pHTML);
where pHTML can be a very large fragment. Is there a more effecient way to inser the fragment (and execute any scripts in the fragment)?
Changed March 28, 2011 11:04PM UTC by comment:6
This is probably related to the same IE8 performance problems reported in #7341 (and other "duplicate" bugs) that were unfortunately dismissed as "won't fix". The comments left by dozens of visitors ALL indicate that they have been forced to downgrade to 1.4.2 because of these performance issues.
Therefore, is this really LOW priority? I think not!
Changed April 17, 2011 05:41AM UTC by comment:7
| resolution: | → duplicate |
|---|---|
| status: | open → closed |