Bug 181192 - Create a post mortem analyser to track floating ClassLoaders
Summary: Create a post mortem analyser to track floating ClassLoaders
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-04-05 09:00 EDT by Karsten Becker CLA
Modified: 2019-09-06 15:31 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karsten Becker CLA 2007-04-05 09:00:49 EDT 
The permgenSpace problem is well known: https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250
And there is no way for eclipse to fix the JVM. But it points to a very specific problem with floating ClassLoaders: http://blogs.sun.com/fkieviet/entry/how_to_fix_the_dreaded
In order to detect those leakages it would be nice to have a post mortem analyser that is started by the native launcher in case of a severe JVM error. In Java6 there is a option -XX:+HeapDumpOnOutOfMemoryError which dumps the memory contents to disk. What one might do is create a tool that analyses this dump and specifically checks for ClassLoaders that are only referenced through Class objects as described here: http://blogs.sun.com/edwardchou/
This tool would help Eclipse plugin developer to fix those cases and thus help to prevent the very annoying permgenSpace problem and decrease the overall memory footprint of Eclipse.
Comment 1 Jeff McAffer CLA 2007-04-06 21:41:37 EDT 
sounds great.  Contributions would be most welcomed...
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:31:27 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.