Eclipse MAT

https://gist.github.com/mrbuk/5726c469234238a26327
nohup ./ParseHeapDump.sh $1 org.eclipse.mat.api:suspects org.eclipse.mat.api:overview org.eclipse.mat.api:top_components -vmargs -Xmx96g -XX:-UseGCOverheadLimit > mat_report.out &

java -Xms8g -Xmx12g -jar  mat.app/Contents/Eclipse/plugins/org.eclipse.equinox.launcher_1*.jar -application org.eclipse.mat.api.parse java_pid2992.hprof org.eclipse.mat.api:suspects org.eclipse.mat.api:overview org.eclipse.mat.api:top_components

http://javaforu.blogspot.com/2013/11/analyzing-large-java-heap-dumps-when.html
https://www.jeroenreijn.com/2010/10/large-heap-dump-analysis-with-eclipse.html
https://wiki.eclipse.org/MemoryAnalyzer/FAQ
java -Xmx6g -jar plugins/org.eclipse.equinox.launcher_1*.jar -consoleLog -application org.eclipse.mat.api.parse path/to/dump.dmp.zip org.eclipse.mat.api:suspects org.eclipse.mat.api:overview org.eclipse.mat.api:top_components

You need to copy all files which are present in that directory to your laptop. I've done this successfully many times. I run the analyser on the server using

The org.eclipse.mat.api:suspects argument creates a ZIP file containing the leak suspect report. This argument is optional.

The org.eclipse.mat.api:overview argument creates a ZIP file containing the overview report. This argument is optional.

The org.eclipse.mat.api:top_components argument creates a ZIP file containing the top components report. This argument is optional.

http://javaforu.blogspot.com/2013/11/analyzing-large-java-heap-dumps-when.html
https://stackoverflow.com/questions/2382024/how-to-use-existing-eclipse-mat-indexes-for-interactive-analysis
You need to copy all files which are present in that directory to your laptop. I've done this successfully many times. I run the analyser on the server using

/opt/mat/MemoryAnalyzer -consolelog -application org.eclipse.mat.api.parse "$@" org.eclipse.mat.api:suspects org.eclipse.mat.api:top_components

https://stackoverflow.com/questions/7254017/tool-for-analyzing-large-java-heap-dumps

Normally, what I use is ParseHeapDump.sh included within Eclipse Memory Analyzer and described here, and I do that onto one our more beefed up servers (download and copy over the linux .zip distro, unzip there). The shell script needs less resources than parsing the heap from the GUI, plus you can run it on your beefy server with more resources (you can allocate more resources by adding something like -vmargs -Xmx40g -XX:-UseGCOverheadLimit to the end of the last line of the script. For instance, the last line of that file might look like this after modification

./MemoryAnalyzer -consolelog -application org.eclipse.mat.api.parse "$@" -vmargs -Xmx40g -XX:-UseGCOverheadLimit

Run it like ./path/to/ParseHeapDump.sh ../today_heap_dump/jvm.hprof

After that succeeds, it creates a number of "index" files next to the .hprof file.

After creating the indices, I try to generate reports from that and scp those reports to my local machines and try to see if I can find the culprit just by that (not just the reports, not the indices). Here's a tutorial on creating the reports.

Example report:

./ParseHeapDump.sh ../today_heap_dump/jvm.hprof org.eclipse.mat.api:suspects

Other report options:

org.eclipse.mat.api:overview and org.eclipse.mat.api:top_components

If those reports are not enough and if I need some more digging (i.e. let's say via oql), I scp the indices as well as hprof file to my local machine, and then open the heap dump (with the indices in the same directory as the heap dump) with my Eclipse MAT GUI. From there, it does not need too much memory to run.

EDIT: I just liked to add two notes :

• As far as I know, only the generation of the indices is the memory intensive part of Eclipse MAT. After you have the indices, most of your processing from Eclipse MAT would not need that much memory.
• Doing this on a shell script means I can do it on a headless server (and I normally do it on a headless server as well, because they're normally the most powerful ones). And if you have a server that can generate a heap dump of that size, chances are, you have another server out there that can process that much of a heap dump as well.

Important note: ParseHeapDump.sh is packaged with the Linux version only, not the OSX version -- eclipse.org/mat/downloads.php