Opened 10 years ago

Last modified 10 years ago

#9358 open bug

Resizable: Memory leak when destroying

Reported by: lsching17 Owned by:
Priority: minor Milestone: none
Component: ui.resizable Version: 1.10.3
Keywords: Cc:
Blocked by: Blocking:


i create a testcase and access a "dummyObject" by closure during "open" event.

If event handlers are detached after "destroy", then the "dummyObject" should be inaccessible and be garbage-collected.

But chrome heapshot shows that the "dummyObject" is still accessible, and i suspect that the event handlers are not detached

Change History (6)

comment:1 Changed 10 years ago by tj.vantoll

Component: ui.coreui.resizable
Status: newopen
Summary: event handler of dialog are not detached when destroy?Resizable: Memory leak when destroying

I'm not exactly sure what's going on here but this appears to be a problem with resizable and not dialog. Hit create and then destroy and the dummyObject instance will not be garbage collected:

Isching17 do you know if Chrome's dev tools give you any help tracking down line numbers / variable names? Or is it just function names? On this example ( _alsoResize is the only specific thing I see and I don't see anything suspicious in there:


comment:2 Changed 10 years ago by lsching17

i am not a chrome expert, but placing the mouse on the related object will show the related information

comment:3 Changed 10 years ago by tj.vantoll

Ah yeah, I meant to say _renderAxis in my previous comment. Still confusing why that would be holding a reference since the instance is gone. That'll help though, thanks.

comment:4 Changed 10 years ago by lsching17

please delete

Last edited 10 years ago by lsching17 (previous) (diff)

comment:5 Changed 10 years ago by lsching17

I created a BAD patch for jquery-ui.js (1.10.3) and linkage seems fixed, but do not know whether the widgets are broken.

::diff removed::

Last edited 10 years ago by Scott González (previous) (diff)

comment:6 Changed 10 years ago by Scott González

@lsching17 If you'd like to propose a change, please sign our CLA and submit a pull request.

Note: See TracTickets for help on using tickets.