From: SourceForge.net <no...@so...> - 2007-03-29 17:49:06
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4234547 By: rc_dickerson I tried profiling the project I'm currently working on (that uses Jung) to see what happened... I have a dialog that contains an extension of VisualizationViewer. The viewer is visualizing an extension of SparseGraph. The Layout being used is my own direct implementation of the Layout interface, and the renderer being used is an extension of PluggableRenderer. I am managing some listeners of the Viewer myself, but have double checked to make sure references are always being removed correctly when the dialog closes. All other listener registration happens inside of Jung libraries. I tried opening and closing the dialog around 50 times at various points throughout my application; the average visualized graph contains only about 4 or 5 nodes. Here are the live jung objects that topped the memory usage chart at that point: http://i9.tinypic.com/2cp7rxh.jpg And here's what it looked like after I forced garbage collection from the profiler: http://i3.tinypic.com/44shytw.jpg No instances of the dialog were around any more at this point. So, it looks like there are indeed quite a few DefaultUserData objects floating around. (I'm not sure why there are 1 or 2 live instances of some other things, but they'd not survived more than a couple of generations, so I'm thinking they'd be gc'd in the near future). It's interesting, though, that after I forced gc, some of those DefaultUserData objects were collected... It's possible that somewhere a reference to this type of object is not being properly released. I took a quick look at some of the code involved, and didn't see anything obvious, but I'll be sure to post about anything I happen to find. Are you doing similar things with your code? (And, are your vm profiles showing similar behavior?) ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=252062 |