> In the past I'm sure I used a tool (possibly jdb) to examine objects
> created in a running jvm. I think I added some arguments to the
[quoted text clipped - 4 lines]
> find the one I used or can't get jdb to do it. Might have to use this
> for 1.4 app but it will be useful whatever version.
Bear in mind that any such profile is transitory. The Hotspot compiler can
change how much memory an object needs at run time through its various
optimizations.
GC complicates matters.
Profiler and GC output are useful for your purpose.

Signature
Lew
Daniel Pitts - 15 Nov 2007 16:20 GMT
>> In the past I'm sure I used a tool (possibly jdb) to examine objects
>> created in a running jvm. I think I added some arguments to the
[quoted text clipped - 12 lines]
>
> Profiler and GC output are useful for your purpose.
There are tools though that help you take a "snapshot" of the memory
used in a JVM. This *can* be useful to track down memory leaks. I
think the tool is hprof, but I'm not sure.
Google for Java Heap Profile, and you'll probably stumble across a
useful tool.

Signature
Daniel Pitts' Tech Blog: <http://virtualinfinity.net/wordpress/>