Yes, Jprobe is fun like that. There is a button on one of the toolbars that will suggest where things are being held from. It gives you an object graph and you get to play with the graph, removing relationships to see what would cause that object to be un-referenced. It has been a few weeks, but I seem to remember looking at a snapshot detail, then pulling up details on the object that I wanted to find references to, then on that window, it was the 3rd or 4th toolbar item from the left. Sorry for the vagueness. I hope that is a little helpful!
David Quoting "Braun-Friedman, David" <[EMAIL PROTECTED]>: > I am currently using a JProbe trial to try and find the memory leaks in > java2D imaging application. I have been able to (I think) identify the > objects which are loitering after they should have been deleted. I have > used jprobe to identify the classes that contain references that should > be eliminated so that the objects can be garbage collected, however I > have really no idea how to find where the references are or how to fix > them...any help or advice would be greatly appreciated. Thanks. > > > Dave > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff JAVA2D-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA2D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
