[Tom McCobb]

I am getting frequent out of memory errors at various points since installing 7.5 (They were a problem with 7.1, too, but not as frequent). Sometimes it is a warning that heap space or Eden space is low, most often it is an OutOfMemory error during deployments (to JBoss).

Here is my installation summary and myeclipse.ini:

*** Date: 
Friday, August 14, 2009 10:09:52 AM EDT

** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.6.0_13


*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.5
Build id: 7.5-20090609


*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 7.5
Build id: 7.5-20090609




Eclipse Plug-in Development Environment

Version: 3.4.2.R342_v20090122-7T7U1E9imVKz-A8Vz-p_jRS
Build id: M20080703-0800


Eclipse Platform

Version: 3.4.2.R342_v20090122-9I96EiWElHi8lheoJKJIvhM3JfVsYbRrgVIWL
Build id: M20090211-1700


Eclipse Graphical Editing Framework GEF

Version: 3.4.2.v20090218-1145-67728084A56B4I233613552
Build id: 200809101400


Eclipse RCP

Version: 3.4.200.R342_v20090122-989JESTEbig-SVaL8UJHcYBr4A63
Build id: M20090211-1700


Eclipse Java Development Tools

Version: 3.4.2.r342_v20081217-7o7tEAoEEDWEm5HTrKn-svO4BbDI
Build id: M20090211-1700




Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\Genuitec\MyEclipse 7.0\myeclipse.exe
-name
Myeclipse
--launcher.library
C:\Program Files\Genuitec\MyEclipse 7.0\../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\Program Files\Genuitec\MyEclipse 7.0\../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar
-configuration
configuration
-vm
C:\Program Files\Genuitec\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\jre\bin\client\jvm.dll

--launcher.library
../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731
-startup
../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar
-configuration
configuration
-vm
C:\Program Files\Genuitec\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\jre\bin\client\jvm.dll
-vmargs
-Xms896M
-Xmx896M
-XX:PermSize=256M

I am using nWire and Tasktop plugins.

[support-joy]

tmccobb,

Thank you for the details. Can you try something – from MyEclipse IDE menu options click on Window > Preferences > General. Mark Show heap status as selected. Can you monitor at what times does the heap shoot up?

Can you look through your error log file and look for any relevant errors? Your error log file is located at [your workspace dir]/.metadata/.log

[Tom McCobb]

The Heap status (which I always have on) read 449 of 889 when I go tht most recent out of Memory error while I was re-deploying from an exploded deployment to a packaged deployment. Here is from the log:

!ENTRY org.eclipse.core.jobs 4 2 2009-08-18 00:20:10.396
!MESSAGE An internal error occurred during: "Add Deployment".
!STACK 0
java.lang.OutOfMemoryError
    at java.io.FileInputStream.readBytes(Native Method)
    at java.io.FileInputStream.read(FileInputStream.java:177)
    at com.genuitec.eclipse.core.datatransfer.ZipFileExporter.write(ZipFileExporter.java:217)
    at com.genuitec.eclipse.ast.deploy.ant.DeployerZipFileExportOperation.exportResource(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.ant.DeployerZipFileExportOperation.exportResource(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.ant.DeployerZipFileExportOperation.exportSpecifiedResources(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.ant.DeployerZipFileExportOperation.run(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.packaging.EarPackager.createBasicEAR(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.packaging.EarPackager.packageAndDistributeEAR1(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.packaging.EarPackager.exportEARProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.exportEARProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.packaging.PackageUtils.exportEARProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.EARDeployment.exportEARProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.EARDeployment.deployAsPackageArchive(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.jobs.A.�(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.jobs.A.run(Unknown Source)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

[support-joy]

tmccobb,

Thank you for the log file and heap status details. What is your hardware configuration meaning hard disk space and RAM?
I will escalate this issue to a dev team member. They will get back to you shortly.

[Tom McCobb]

The partition that Eclipse runs from is 68GB with 32GB free; JBoss is on another partition of 164GB with 97GB free. This is a fairly new disk drive, fwiw, so it is clean and unfragmented.

RAM is 4GB, OS is XP2 – so I only “see” about 3.5GB

[Loyal Water]

Can you replace the memory arguments in the eclipse.ini file with the values suggested in this post. Does that help?
http://www.myeclipseide.com/PNphpBB2-viewtopic-t-10087-highlight-memory.html

[Tom McCobb]

Not only did that NOT work, (OutofMemory errors when starting Eclipse while initializing tools), when I went to change it back to the original settings in the myeclipse.ini, it would not start with more than 64M of heap memory. I actually had to remove the -vmargs from the .ini file and place them in the shortcut command line to get Eclipse to start (after a re-boot it would fail when trying to load the workspace).

[support-joy]

I will escalate this to a dev team member. They will get back to you shortly.
Sorry for the inconvinience.

[Loyal Water]

I think you have entered the command line args wrong… they need to be on separate lines, not just copied into 1 long line like that… if you saw a failure on startup that is probably what was wrong.

Can you try putting the args on different lines and testing this again for me. Does it help?

[Tom McCobb]

the -XX:ReservedCodeCacheSize=64m seems to help; the errors are less frequent. Still occasional problems that seem to occur mainly if I am doing a lot of copying and pasting between editor screens.

But the problem with OutOfMemory errors while deploying to an EAR persists. I had a lot of trouble last night with multiple attempts (about 6-8) to create an EAR failed with the error. I noticed int he log (since scrolled off) that there were errors about not being able to delete files in …/.myeclipse/build/… folder.
Manually deleting the referenced folder (most of the files were actually gone) and rebooting my computer resolved the issue.

Note that the OutOfMemory only occurs with packaged deployments, and after several exploded deployments of the same project.

[Loyal Water]

Note that the OutOfMemory only occurs with packaged deployments, and after several exploded deployments of the same project.

Are you manually doing the exploded deployment several times? An exploded deployment should redeploy the changes automatically so you should not be redeploying manually. You facing the out of memory issue with the automatic redeployment?

[Tom McCobb]

The problem got to the point where I could not build anything, even if hte build was the first thing I did after starting MyEclipse.

I found that setting the -Xmx vmarg to 768M from 896M seems to have solved the problem. I had the -Xmx setting cranked up to run the JProbe plugin, but I don’t run JProbe inside of Eclipse right now.

[Author]

Posts