Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#15907 closed defect (fixed)

possible memory leaks after destroying a gfx surface.

Reported by: Patrick Ruzand Owned by: Patrick Ruzand
Priority: high Milestone: 1.7.4
Component: DojoX GFX Version: 1.7.0
Keywords: Cc: ben hockey
Blocked By: Blocking: #14589

Description

When a Surface is destroyed, the children are not properly destroyed (i.e. their destroy() method is not called), leading to pending references to the children in the gfx registry.

Change History (10)

comment:1 Changed 7 years ago by Patrick Ruzand

Owner: changed from Eugene Lazutkin to Patrick Ruzand
Status: newassigned

comment:2 Changed 7 years ago by Patrick Ruzand

Milestone: tbd1.8.1
Priority: undecidedhigh

comment:3 Changed 7 years ago by ben hockey

Cc: ben hockey added

comment:4 Changed 7 years ago by Patrick Ruzand

Resolution: fixed
Status: assignedclosed

In [29601]:

fix Surface.destroy() MLKs. fixes #15907, !strict

comment:5 Changed 7 years ago by Patrick Ruzand

In [29602]:

fix Surface.destroy() MLKs. refs #15907, !strict

comment:6 Changed 7 years ago by cjolif

Blocking: 14589 added

(In #14589) With the latest commits we are down to 0 leaked shapes in the updated test case for trunk and 1.8 branch. 1.7 branch fix is waiting for gfx #15907 being backported to 1.7 branch.

comment:7 Changed 7 years ago by cjolif

Resolution: fixed
Status: closedreopened
Version: 1.8.01.7.0

The problem was already there in 1.7.x. Ideally I would like to get that fixed in 1.7.x as well so that charting can be fixed accordingly.

comment:8 Changed 7 years ago by Patrick Ruzand

In [29611]:

backport to 1.7.4. fix Surface.destroy() MLKs. refs #15907

Last edited 7 years ago by Patrick Ruzand (previous) (diff)

comment:9 Changed 7 years ago by Patrick Ruzand

Resolution: fixed
Status: reopenedclosed

comment:10 Changed 7 years ago by cjolif

Milestone: 1.8.11.7.4
Note: See TracTickets for help on using tickets.