[FMR-1]

I’ve been receiving the following error message several times a day:

MyEclipse has detected that less than 5% of the 64MB of Perm Gen (Non-heap memory) space remains.

It is strongly recommended that you exit and restart MyEclipse with new virtual machine
memory paramters to increase this memory. Failure to do so can result in data loss.

The recommended Eclipse memory parameters are:
eclipse.exe -vmargs -Xms128M -Xmx512M -XX:PermSize=64M -XX:MaxPermSize=128M

My <MyEclipse root>\eclipse\eclipse.ini contains the following:

-vmargs -Xms128M -Xmx512M -XX:PermSize=128M -XX:MaxPermSize=256M

Originally it had 64M for PermSize. Any ideas why I’m still receiving this error message?

Thanks,
Leo

[FMR-1]

In case it helps, this is what I see when I exit:

—————————
Eclipse
—————————
JVM terminated. Exit code=1
C:\Program Files\MyEclipse\jre\bin\javaw.exe
-jar C:\Program Files\MyEclipse\eclipse\startup.jar
-os win32
-ws win32
-arch x86
-launcher C:\Program Files\MyEclipse\eclipse\eclipse.exe
-name Eclipse
-showsplash 600
-exitdata b04_58
-vmargs -Xms128M -Xmx512M -XX:PermSize=128M -XX:MaxPermSize=256M
-vm C:\Program Files\MyEclipse\jre\bin\javaw.exe
-vmargs
-jar C:\Program Files\MyEclipse\eclipse\startup.jar
—————————
OK
—————————

[FMR-1]

No one has any ideas why this is still happening even though my settings are as suggested by the MyEclipse team? I’m still having to restard the IDE several times a day. Other members of my team are having similar problems.

[FMR-1]

Maybe this will help. Here is what my .log file is showing:

!SESSION 2007-03-15 16:02:27.371 ———————————————–
eclipse.buildId=M20060921-0945
java.version=1.5.0_08
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -vmargs -Xms128M -Xmx512M -XX:PermSize=64M -XX:MaxPermSize=256M
Command-line arguments: -os win32 -ws win32 -arch x86 -vmargs -Xms128M -Xmx512M -XX:PermSize=64M -XX:MaxPermSize=256M

!ENTRY org.eclipse.wst.internet.cache 1 0 2007-03-15 16:03:06.402
!MESSAGE wtp.autotest.noninteractive is set. Licenses dialogs will not be displayed.

!ENTRY org.eclipse.osgi 4 0 2007-03-15 16:03:49.182
!MESSAGE While loading class “org.tigris.subversion.subclipse.ui.console.ConsoleDocument$ConsoleLine”, thread “main” timed out waiting (5000ms) for thread “Worker-1” to finish starting bundle “org.tigris.subversion.subclipse.ui”. To avoid deadlock, thread “main” is proceeding but “org.tigris.subversion.subclipse.ui.console.ConsoleDocument$ConsoleLine” may not be fully initialized.
!STACK 0
java.lang.Exception: Generated exception.
at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.preFindLocalClass(EclipseLazyStarter.java:75)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:409)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:334)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:386)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:347)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at org.tigris.subversion.subclipse.ui.console.ConsoleDocument.getLines(ConsoleDocument.java:79)
at org.tigris.subversion.subclipse.ui.console.SVNOutputConsole.dump(SVNOutputConsole.java:202)
at org.tigris.subversion.subclipse.ui.console.SVNOutputConsole.access$1(SVNOutputConsole.java:199)
at org.tigris.subversion.subclipse.ui.console.SVNOutputConsole$1.run(SVNOutputConsole.java:124)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3325)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)

!ENTRY org.eclipse.core.resources 2 1 2007-03-15 16:16:08.734
!MESSAGE Skipping builder org.hibernate.eclipse.console.hibernateBuilder for project sharespoc. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.

[Scott Anderson]

Ah, this helps quite a lot. You’ll notice that the stack that generated the exception goes through your Subversion plugin, not through MyEclipse. If it had a memory leak of some sort and was causing issues, that would explain why it would show up for you and your team, but not for other MyEclipse users or in testing since there is no reason MyEclipse would need more permgen space than you’re configuring.

On the other hand:

MyEclipse has detected that less than 5% of the 64MB of Perm Gen (Non-heap memory) space remains.

That message shows that the runtime only thinks you have 64MB of PermGen (-XX:MaxPermSize) configured which is below the settings you’ve configured in. So, if the commandline options specify a max of 256M, why is only 64MB being configured? Can you try raising -XX:PermSize=128M ?

[Author]

Posts