Is there any way to analyze a truncated Java Heap Dump (hprof file)? : <p>In my work, we are running into a difficult to reproduce OOM issue. Or, more accurately, it is very easy to reproduce on one system, making that system unusable, but difficult to reproduce anywhere else, given the same inputs.</p>

<p>The application is being run as a service using a service wrapper. We did manage to get the configuration changed to launch it with the option of outputting a heap dump file on OOM but, unfortunately, they were truncated, most likely due to the service wrapper timing out and killing the process as it wrote the file. This is readily apparent, since the max memory is set to 1GB, and the hprof files are as small as 700MB, which is too small to be the entire heap upon OOM.</p>

<p>It would take a lot of jumping through hoops to additionally configure the wrapper to give the java process a longer time to write out the heap, but we are pursuing this using these 2 options:</p>

<pre><code>wrapper.jvm_exit.timeout=600
wrapper.shutdown.timeout=600
</code></pre>

<p>The question is, is there anything useful I can do with the truncated hprof files I have? Eclipse MAT chokes on them. Jhat appears to load them, but then only shows 3 instances of Java.Object of size 0 and nothing else. I tried YourKit and it couldn't write its oids file.</p>

<p>It seems to me like these files should have some useful, accessible information in them. Is there a tool that can read what's there?</p>

<p>Thank you for your time!</p>
