Opened 10 years ago

Closed 9 years ago

#10556 closed defect (fixed)

Possible memory leak in dojox.widgets.portlet

Reported by: abhishekgd Owned by: Shane O'Sullivan
Priority: high Milestone: 1.5
Component: DojoX Widgets Version: 1.4.0
Keywords: memory leak, portlet Cc:
Blocked By: Blocking:

Description

I have a bunch of portlets inside a grid container inside a border container which is wrapped inside a content pane, "page".

Now, when I do a page.destroyRecursive() it deletes all the descendants and the page itself but I can still do a dijit.byId for the portlet settings node though I can't find it in the dom.

I have attached a test case.

Attachments (1)

test_memory_leak.html (3.5 KB) - added by abhishekgd 10 years ago.
Test case for portlet memory leak

Download all attachments as: .zip

Change History (6)

Changed 10 years ago by abhishekgd

Attachment: test_memory_leak.html added

Test case for portlet memory leak

comment:1 Changed 10 years ago by abhishekgd

In firebug if I do:

dijit.byId('page').destroyRecursive() , it clears all the elements but if I do:

dijit.byId('lineChartPortlet') or it's children it still returns a widget reference. For all its parent nodes, nothing is returned.

comment:2 Changed 9 years ago by dante

Owner: changed from dante to Shane O'Sullivan

comment:3 Changed 9 years ago by Shane O'Sullivan

Does the same happen with the dijit.TitlePane?? The Portlet is really just a TitlePane?, which adds some icons to the title bar.

comment:4 Changed 9 years ago by Shane O'Sullivan

(In [22054]) Refs #10556 Fixes memory leak when destroying Portlets and TableContainer? widgets

comment:5 Changed 9 years ago by Shane O'Sullivan

Resolution: fixed
Status: newclosed

Fixed this issue, also with the TableContainer?, in [22054], closing.

Note: See TracTickets for help on using tickets.