Opened 3 years ago

Last modified 21 months ago

#10667 open bug

Draggable: $.ui.ddmanager.current not released on draggable _destroy

Reported by: eshcharc Owned by:
Priority: minor Milestone: none
Component: ui.draggable Version: 1.11.1
Keywords: Cc:
Blocked by: Blocking:


In the days of client side frameworks and SPAs, considerations need to be made regarding client side page switch and optimizations and cleaning of assets.

When we examined and profiled our SPA on a page switch scenario, we've noticed that a jQuery-UI plugin is holding a whole element tree. A further examination led us to a draggable and the "global" $.ui.ddmanager.current.

It seems that when a draggable is being destryed via _destroy, $.ui.ddmanager.current which is linked to this draggable, is not taken care of and keep a reference to the draggable and all of its tree elements. When a client side framework is involved, that makes it worse.

That can quite easily be treated.

Change History (3)

comment:1 Changed 2 years ago by Scott González

Component: ui.coreui.draggable

comment:2 Changed 2 years ago by tj.vantoll

Status: newopen
Summary: $.ui.ddmanager.current not released on draggable _destroyDraggable: $.ui.ddmanager.current not released on draggable _destroy

comment:3 Changed 21 months ago by merildev

Same problem here.

I use Backbone for my SPA, when the view which contains the draggable element is closed, the DOM tree should be deleted. However, I can see a leak and my view appears as a detached DOM tree with some references in the JS code (jQuery UI).

Quick and dirty solution: If I do a 'delete $.ui.ddmanager.current;' when the view is closed, the reference is removed and the garbage collector is able to delete the DOM nodes.

Last edited 21 months ago by merildev (previous) (diff)
Note: See TracTickets for help on using tickets.