Well, that was great, but if I needed a strong machine to run Auto-MAT, I would still have to find a machine, upload the heap dump, install docker if it is not installed, and then download everything back or store it somewhere. But if you need a deeper drill down into the memory, you could open the heap dump with MAT and, since the indexes are already there, Eclipse MAT will open in a snap. Suspects and Overview.Īfter running this, it will usually be enough to open the HTML reports to understand the problem. This will parse the heap dump, create indexes and will generate nice 2 HTML reports. Now every time I need to analyse a heap dump I could just run something like:ĭocker run -it -mount src=$(pwd),target=/data,type=bind /jfrog/auto-mat heap1.hprof 11g suspects,overview

So, I decided to wrap it in a docker container, and that is how Auto-MAT got created. What if I wanted to run it on Mac or Windows? Also, Eclipse MAT requires Java to be installed. But, it comes only with the linux installation.

I've tried the script and it worked great. This is much better than the experience I had, I could run the script on a remote server from terminal, which is easy to set up, and I usually have a couple of servers ready to do some work for me. The index files will help Eclipse MAT open in seconds, instead of long hours. The script will calculate indexes for later use in eclipse MAT and can also generate some nice HTML reports that are usually good enough to understand the problem. You can use a script that comes with the Linux installation of Eclipse MAT. So I looked around, and discovered that you can let Eclipse MAT parse the heap dump from commandline! Running a server with GUI in the cloud is not something I do every day, and it took some time to configure the server, start it, connect with remote desktop etc'. I had to use GUI for that, because all the tools I knew back then required GUI to operate. I eventually took a strong machine with GUI in the cloud and got it to work, but the experience was bad. I usually use Eclipse MAT for the job, but this time, it was so large the tool could not parse the heap dump in an acceptable time, and required more and more memory. A while ago, I had to analyse a large java heap dump, generated by one of our servers after a memory leak.

Download eclipse memory analyzer