| Load 3,4 GB 64 bits dump on 32 bits [message #8744] |
Wed, 11 February 2009 08:16  |
Eclipse User |
|
|
|
A dump file was generated on an linux 64 bits machine (jdk 6 u10). The
dump was generated by command line: jmap -dump:file=dump.bin
Used ParseHeapDump.sh on the same machine to generate the index files (see
below), copied those index files to my laptop (2 GB RAM)
a2s.index
domIn.index
domOut.index
idx.index
inbound.index
index.index
o2c.index
o2hprof.index
o2ret.index
outbound.index
I can open the dump file on MAT and open the dominator tree, but opening
the leak suspects report, trigger a new parser operation and after some
hours, there is an OOME (java heap space)
Is there any way to generate leak suspects on command line, as
ParseHeapDump.sh ?
Thanks
Claudio Miranda
|
|
|
| Re: Load 3,4 GB 64 bits dump on 32 bits [message #8770 is a reply to message #8744] |
Wed, 11 February 2009 13:02  |
| Eclipse User |
|
|
|
> I can open the dump file on MAT and open the dominator tree, but opening
> the leak suspects report, trigger a new parser operation and after some
> hours, there is an OOME (java heap space)
Strange. If the MAT versions are identical on both machines, then parsing
should not happen again. The leak suspect report is using nothing special
here.
Are you sure that it is deleted the index files and re-parsing?
However, depending on your leak, the leak report itself might have a
problem. We have seen in the passed, that certain type of leaks are
problematic. Therefore we added some sampling. Maybe we need to add some
more. You could help by taking a thread dump during the long operation.
> Is there any way to generate leak suspects on command line, as
> ParseHeapDump.sh ?
Yes. The syntax is strange, but add "org.eclipse.mat.api:suspects"
(without ") as an additional argument after the heap dump.
Similar to
http://wiki.eclipse.org/index.php/MemoryAnalyzer/FAQ#How_to_ run_on_64bit_VM_while_the_native_SWT_are_32bit
Andreas.
|
|
|
Powered by
FUDForum. Page generated in 0.02934 seconds
Home