Community
Participate
Working Groups
3.3 M5 Doing a leak check on our views, I found one of our views still being held onto (after it was closed) via an Identifier. Although the MutableActivityManager references the Identifier via a WeakHashMap, the ProxyActivityManager can reference the same Identifier via a strong reference. It's easier to show you in the profiler than to make sense of an attached profile.
To clarify: the reference chain between the view and the Identifier's goes through several ViewPluginAction and ObjectPluginAction instances.
Also note that I had activated another view before taking the snapshot, so I don't think this is a dup of the other recent leak bug I filed.
Paul, is this a dup of bug 174908?
(In reply to comment #3) > Paul, is this a dup of bug 174908? I suspect that it is (I was going to check your data first). In M5 you could leak a part by using a context menu submenu or by simply by popping up a context menu and closing a part. We fixed both of those, but recently. The ViewPluginActions shouldn't be a problem (they were always disposed), and I'm pretty sure I've fixed the ObjectPluginAction (which were being leaked along with the PluginActionContributionItems. PW
Is the fix in the last I-build? If so, I can test the fix out. I was definitely seeing Identifier -> ViewPluginAction -> view in the ref graph.
Yes, the fix would be in I20070403 PW
*** This bug has been marked as a duplicate of bug 174908 ***