.detach memory leak.
I don't know if this is being fixed or is fixed in the most recent versions, but in 1.4.2, when I detached an element in DOM and then reinserted into another place, jQuery left something in memory...leaked. I found that I had to call the .detach and then on the next line also .remove the same element to avoid the leak. This became a big problem as I was scripting an animation for the screen with lots of detaching and appending. Saw the memory go from 80k to almost 1 gig. Not good.
Is there even a time when you would want to detach and still have a remnant in memory somewhere? The very fact that you detach something means it is pulled from the DOM and stored in an new object. That new object can now be reinserted. Shouldn't detach first pull the element out, put it in an object and then .remove it automatically? What value can that element have anywhere in memory outside of the object you just created?
Is there even a time when you would want to detach and still have a remnant in memory somewhere? The very fact that you detach something means it is pulled from the DOM and stored in an new object. That new object can now be reinserted. Shouldn't detach first pull the element out, put it in an object and then .remove it automatically? What value can that element have anywhere in memory outside of the object you just created?
Topic Participants
gsgriffin
Dave Methvin