This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When you simply subscribe and then unsubscribe from a public conversation, without even opening it, there are some objects left on heap. See the attached OptimizeIt window for reference chain of leaked PublicConversationNode. I see also other objects, like e.g. PublicConversationOpenSupport and PublicConversationOpenSupportEnv leaking.
Created attachment 24631 [details] OptimizeIt screenshot
Working on it. PublicConversationOpenSupport keeps reference to Conversation even it is closed and left.
A part of the problem was fixed in the service library...
Seems like two WeakListeners can do a miracle. Testing a fix.
Fixed in trunk collab/ui/src/org/netbeans/modules/collab/ui/PublicConversationNode.java,v1.3 AU: Collab/UI v1.3
Backported the fix to release50: collab/ui/src/org/netbeans/modules/collab/ui/PublicConversationNode.java,v1.2.8.1 Release50 AU: Collab/UI v1.1.1