http://schneide.wordpress.com/2008/10/20/java-solves-all-memory-problems-or-maybe-not/ public business secrets Tue, 15 Dec 2009 11:36:11 +0000 http://wordpress.com/ hourly 1 http://schneide.wordpress.com/2008/10/20/java-solves-all-memory-problems-or-maybe-not/#comment-97 Analyzing Java Heap problems Part 2: Using Eclipse MAT « Schneide Blog Mon, 29 Dec 2008 12:59:05 +0000 http://schneide.wordpress.com/?p=89#comment-97 [...] The histogram is somewhat similar to what jHat offers. It allows you to browse, sort and filter the object instances in memory and shows you instance count and the shallow heap (memory used only by this object instance) and retained heap (memory used by this object instance including referenced objects). From the context menu you can choose “Merge Shortest Paths to GC roots” to see the reference chain of an object all the way up to the classloader. Here we can see that the JDateChooser registers itself at the MenuSelectionManager as a listener which can cause serious memory leaks as described in another post about Java memory handling. [...] [...] The histogram is somewhat similar to what jHat offers. It allows you to browse, sort and filter the object instances in memory and shows you instance count and the shallow heap (memory used only by this object instance) and retained heap (memory used by this object instance including referenced objects). From the context menu you can choose “Merge Shortest Paths to GC roots” to see the reference chain of an object all the way up to the classloader. Here we can see that the JDateChooser registers itself at the MenuSelectionManager as a listener which can cause serious memory leaks as described in another post about Java memory handling. [...]

]]> http://schneide.wordpress.com/2008/10/20/java-solves-all-memory-problems-or-maybe-not/#comment-91 Observer/Listener structures in C++ with boost’s smart pointers « Schneide Blog Mon, 08 Dec 2008 16:36:53 +0000 http://schneide.wordpress.com/?p=89#comment-91 [...] of issues can be hard to get right Java has this nice little helper, the garbage collector. But as Java solves all memory problems, or maybe not? points out, you can still easily shoot yourself in foot or even blow your whole leg away.  One of [...] [...] of issues can be hard to get right Java has this nice little helper, the garbage collector. But as Java solves all memory problems, or maybe not? points out, you can still easily shoot yourself in foot or even blow your whole leg away.  One of [...]

]]> http://schneide.wordpress.com/2008/10/20/java-solves-all-memory-problems-or-maybe-not/#comment-65 Analyzing Java Heap problems Part 1: Basic actions and tools « Schneide Blog Mon, 03 Nov 2008 13:38:19 +0000 http://schneide.wordpress.com/?p=89#comment-65 [...] issues but how do you find out if that is true and what is taking up all that memory? Knowing the potential problems is fine. Nevertheless you still have to find out your actual problems. There are several [...] [...] issues but how do you find out if that is true and what is taking up all that memory? Knowing the potential problems is fine. Nevertheless you still have to find out your actual problems. There are several [...]

]]>