Manuscript (Case [Issue]22163) GTools - Memory Leak: GLMHintableActionButtonBrick

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Manuscript (Case [Issue]22163) GTools - Memory Leak: GLMHintableActionButtonBrick

Pharo Issue Tracker
Manuscript Notification
avatar
Marcus Denker opened Case 22163: Memory Leak: GLMHintableActionButtonBrick and assigned it to Everyone:
Bug in Project:  GTools: Misc  •  You are subscribed to this case
John Writes:

 

I found a memory leak in GLMHintableActionButtonBrick. It has an
asyncTask class instance variable that holds a GLMAsyncTask. After
running for a while -- opening and closing inspectors and other tools, I
closed several windows, did a GC and expected to not have any AST nodes
hanging around. However, I found several, so I used my ReferenceFinder
tool to find a reference path. That path went through the
GLMHintableActionButtonBrick to a GLMAsyncTask to a block that holds a
reference to a GLMHintableActionButtonBrick instance. Following
references out of the GLMHintableActionButtonBrick instance eventually
leads to a NodeMorph which has a NodeModel that contained my AST node.
Priority Priority: 5 – Fix If Time Status Status: Work Needed
Assigned To Assigned to: Everyone Milestone Milestone: Pharo7.0

Go to Case
No longer need updates? Unsubscribe from this case.

Don't want Manuscript notifications anymore? Update your preferences.

Manuscript

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker