[leili]

Hi all, here’s what I got on an hourly basis while coding in Eclipse:

MyEclipse has detected that less than 5% of the 945MB of Tenured Gen (heap memory) space remains.

It is strongly recommend that you exit and restart MyEclipse with new virtual machine memory parameters 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

This message will occur after 20 or 30 code saves in Eclipse–meaning press “Ctrl-S” to save the changes and trigger the workspace building.

I’m using Eclipse 3.2.1 and MyEclipse 5.1.0. Tthe jre is jdk1.5.0_14. Here’s my Eclipse ini:

-vmargs
-Xms512M
-Xmx1024M
-XX:PermSize=128M
-XX:MaxPermSize=256M

Any thought as to how to fix it?

[Loyal Water]

Can you start MyEclipse from the console using the following command:-

eclipse.exe -vmargs -Xms128M -Xmx512M -XX:Permsize=64M -XX:MaxPermSize=128M 

Sometimes the arguments are not picked up from the eclipse.ini file due to an extra line break or space between arguments. I just want to make sure that is not the case here.

Let me know if you get the error again after starting it from the command line.

[leili]

Actually I tried the command line mode in the first place, and it didn’t work. Same behavoir, same error message. Clearly the arguments are passed correctly to Eclipse, at least for the heap size, because the “show heap status” tells me it’s using 1016 M memory.

[Loyal Water]

Can you go to MyEclipse > Installation Summary > Installation Details and paste the info here for me.

Why don’t you upgrade to MyEclipse 6.0.1? Im sure using the pulse launcher would sort this issue out.

[leili]

Here it is:

*** Date:
Friday, January 25, 2008 12:38:37 PM PST

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.6.0_03

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 5.1.0 GA
Build id: 20061111-5.1.0-GA

*** Eclipse details:
Eclipse SDK

Version: 3.2.1
Build id: M20060921-0945

Eclipse Graphical Editing Framework

Version: 3.2.1.v20060921
Build id: 20060921-1617

Eclipse Project SDK

Version: 3.2.1.r321_v20060801-tQ1w49KnTArT0FZ
Build id: M20060921-0945

Eclipse Platform

Version: 3.2.1.r321_v20060921-b_XVA-INSQSyMtx
Build id: M20060921-0945

Eclipse Plug-in Development Environment

Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
Build id: M20060921-0945

Eclipse RCP

Version: 3.2.1.r321_v20060801-2ekW2BxmcpPUOoq
Build id: M20060921-0945

Eclipse Java Development Tools

Version: 3.2.1.r321_v20060905-R4CM1Znkvre9wC-
Build id: M20060921-0945

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\eclipse3.2\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
12e0_84
-vm
C:\WINDOWS\system32\javaw.exe

[leili]

I just realized I was using java 1.6 to run eclipse and java 1.5.0.14 to run projects all the time, so I switched back to java 1.5.0.14 for both.

Just tried it out, the memory problem is still there

*** Date:
Friday, January 25, 2008 12:48:54 PM PST

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_14

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 5.1.0 GA
Build id: 20061111-5.1.0-GA

*** Eclipse details:
Eclipse SDK

Version: 3.2.1
Build id: M20060921-0945

Eclipse Platform

Version: 3.2.1.r321_v20060921-b_XVA-INSQSyMtx
Build id: M20060921-0945

Eclipse RCP

Version: 3.2.1.r321_v20060801-2ekW2BxmcpPUOoq
Build id: M20060921-0945

Eclipse Java Development Tools

Version: 3.2.1.r321_v20060905-R4CM1Znkvre9wC-
Build id: M20060921-0945

Eclipse Plug-in Development Environment

Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
Build id: M20060921-0945

Eclipse Project SDK

Version: 3.2.1.r321_v20060801-tQ1w49KnTArT0FZ
Build id: M20060921-0945

Eclipse Graphical Editing Framework

Version: 3.2.1.v20060921
Build id: 20060921-1617

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\eclipse3.2\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
51c_84
-vm
C:\jdk1.5.0_14\jre\bin\javaw.exe

[leili]

in case you need it, here’s my eclipse shortcut:

C:\eclipse3.2\eclipse.exe -vm “C:\jdk1.5.0_14\jre\bin\javaw.exe” -vmargs -Xms512M -Xmx1024M -XX:PermSize=128M -XX:MaxPermSize=128M

[Loyal Water]

reasoner,
What editor were you working in when you got the low memory warning ? Do you have any 3rd party plugins installed along with MyEclipse ?

[leili]

usually it’s Java editor, the only extra plugin I installed is XMLBuddy. Will it help if I set the XX:NewRatio to a higher %?

[Riyad Kalla]

reasoner,
Something fishy is going on with your setup… using plain Eclipse or MyEclipse (which doesn’t instrument the Java editor in any way) should work with 256mb heap but preferablly a 512mb heap… the fact that you can blow out your 1GB heap with only editing and saving in the Java editor points to something very strange going on.

Would you be willing to go to the MyEclipse download page (http://www.myeclipseide.com/modules.php?name=Downloads&file=dl_options) agree to the license, click the MyEclipse 6.0 downloads, then click download option #3 (Pulse optimized Mirror) and run MyEclipse through Pulse that way? It will automatically download MyEclipse and run it, from there, you can reopen your existing workspace and continue working… see if the behavior persists.

If it doesn’t, then we may have narrowed down it was either the previous JRE or your install that had something going on with it that was eating the heap up so quickly.

[Author]

Posts