thanks for the hint. I tried that in the past, but the dump was far too large and jhat always crashed. All versions r225 to r231 allocate millions of small objects.
Will see if it helps now.
Date: Wed, 14 Nov 2012 11:02:03 +0100
From: jiri.klement@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] splitter improvements
Hi,
in case you have trouble with reproducing the problem, there is java option -XX:-HeapDumpOnOutOfMemoryError. Uli can run splitter with this option and then send you produced hprof file which you can open in MemoryAnalyzer or jhat. There you will see all allocated objects, what takes most memory and in case of memory leaks what keeps objects in memory.
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev