Opened 13 years ago
Closed 13 years ago
#5906 closed bug (fixed)
IE leaks memory when removing child elements with bound events (until page is unloaded)
Reported by: | ajpiano | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.4.1 |
Component: | event | Version: | 1.4 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
This is somewhat vague as it is coming in from a third party, however, initial analysis of .remove() on a container with child elements that have bound events appears to cause memory to balloon in IE until the page is unloaded.
Granted, this is far from a performant approach to creating and binding elements, but it's worth investigating.
Attachments (1)
Change History (3)
Changed 13 years ago by
Attachment: | ie_memleak.htm added |
---|
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
Component: | unfilled → event |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
The bad news is that this is a memory leak that appears to be new in 1.4. http://jsbin.com/ewone/9 is the same code in 1.3.2. The elements can be added and removed and the memory stays within the same area, whereas it balloons in 1.4.