Modify ↓
Ticket #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: | ||
| Blocking: | Blocked by: |
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
-
ie_memleak.htm
(877 bytes) -
added by ajpiano 3 years ago.
Change History
comment:1 Changed 3 years ago by ajpiano
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.
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
Note: See
TracTickets for help on using
tickets.