A new version of the Eclipse Memory analyzer is available for
download and from the
update site.
This is the last 0.8 release and from now on working on the
1.0 release will start.
This is a bug fix release and here's the list of the most important bugs fixed:
294350 StackOverflowError in ArrayUtils.hybridsort 270777 The dialog font not apply to the ArgumentWizard 281311 Merged Paths from GC roots calculation may slow down the Leak Suspects report 273915 New resolvers URL, Point and Rectangle 299283 Allow dynamic specification of file extensions for parsers 299497 DTFJ Adapter retains memory 272887 No JvmInfo in Heap Dump details pane 274539 Overview pane is missing scroll bars 297458 Single object queries have a confusing dialog box 254864 Leaking Memory after closing the Heap Dump Editor
13 comments:
This is great Markus. Keep it up!!!
Awesome work!
I'm anxiously awaiting the 1.0 release ;)
Hey Markus, you should be syndicated on PlanetEclipse! Can you please file a bug to get syndicated!?
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=PlanetEclipse.org
Thanks Chris!
I will file a bug.
Cheers,
Markus
Markus, congratulations to the new release! Cheers, Lars
Congratulations and please keep up your excellent work. I am still promoting this excellent piece of software where- and whenever I can.
Hi All,
We have been facing the problem of heap dumps getting generated in our QA Env, the size of the dumps is over 1 GB and the format is .phd
We have tried various tools to analyze it including ones that are mentioned on IBM Website but get the following error
Opening 'heapdump.20110203.030312.831726.0005.phd' as a 'Portable Heap Dump file' ...
Fatal exception : java.lang.Error: Unexpected error: java.io.EOFException
at HR.input.NPHDParserImpl.(NPHDParserImpl.java:96)
at HR.input.PHDParser.open(PHDParser.java:49)
at HR.main.Launcher.openFile(Launcher.java:70)
at HR.main.Launcher.run(Launcher.java:99)
at HR.main.Launcher.main(Launcher.java:41)
The other methods of using Memory Analyzer have also not yielded any success. In one of the tutorials, it was mentioned to write a class which would eventually leak memory and then run it using -XX:+HeapDumpOnOutOfMemoryError. I have the following Questions
1) Has anyone done an analysis of .phd formats over 1.5 GB, if yes - How
2) I have the entire source code from my project and write a class in it which leaks memory, the Memory Analyzer Report which I get does not show anything about the other classes that I have, What am I not doing correctly here
Please let me know
Another option that we are tying is to generate heap dumps in .txt format.
Hi Amit,
Even I am facing the same issue. Getting the same exception. If you were you able to resolve it, please let me know.
Post a Comment