Community
Participate
Working Groups
My Eclipse starts freezing after a while. I can be doing anything from creating a new project to hitting the search button on the toolbar. There is really nothing in particular you can do to reproduce this bug. Eclipse will hang and never recover, with javaw taking almost all of the CPU time. I have the Callisto release of Eclipse with all the Callisto plugins installed. Attached is two stack traces I have captured.
Created attachment 45906 [details] Stack Trace after Eclipse freezes
Created attachment 45907 [details] Stack Trace after Eclipse freezes
*** Bug 149947 has been marked as a duplicate of this bug. ***
Werner Could you also let me know how much memory you have and which vm you are using please?
Looking at your traces you have the following Thread in both: "Low Memory Detector" daemon prio=6 tid=0x0031fa18 nid=0xd18 runnable [0x0000000 0..0x00000000] which indicated that you are pushing the limits of your machine and that likely your java heap is so big that the vm is causing constant memory swapping. Do you run with the heap status (Preferences->General->Show Heap Status). If you run with this you will hopefully be able to see which operation is causing the memory spike
I have an Intel 3.2 Ghz, 1 Gig memory and Java VM 1.5 update 6. I am running with the heap monitor and normally when it freezes it shows about half full. I tried starting Eclipse with -vmargs -XX:MaxPermSize=256m and have not experienced a hang up again (touch wood). Will see what happens on Monday.
(In reply to comment #4) > Werner > > Could you also let me know how much memory you have and which vm you are using > please? > I have the same situation and editted bug 146800 with additional info. I am running 1gig and vm 1.5b4. These are my startup options: C:\Eclipse32Callisto\eclipse\eclipse.exe -console -vmargs -Xmx512M I will try the -XX:MaxPermSize=256m as well.
This -vmargs -XX:MaxPermSize=256m has definitaly made a difference. Haven't had a freeze again. Will still monitor for a few days.
(In reply to comment #7) > I will try the -XX:MaxPermSize=256m as well. My problems seem to be over with the maxpermsize added. I will keep Eclipse open for a few days.
OutOfMemory errors are fairly easy to replicate in this scenario. When I install all of Callisto and then load the ui plug-ins and the ui test suites we get an OutOfMemory error about halfway through the run. I experimented with commenting out the early startup code and it runs fine so it appears to be the memory requirements of the early startup plug-ins. My workbench with a full Callisto install has a 127M heap so I don't think it is possible to run with everything loaded without running without using the -Xmx or -XX:MaxPermSize parameter.
Here are the early startup plug-ins org.eclipse.update.scheduler org.eclipse.update.scheduler org.eclipse.birt.report.debug.ui org.eclipse.cdt.make.ui org.eclipse.hyades.statistical.ui
Why is org.eclipse.update.scheduler in the list twice?
Running with -vmargs -Xms64M -Xmx512M still causes eclipse to hang. It only stopped hanging when I added the MaxPermSize.
Note that the "Low Memory Detector" thread is a standard thread in the Sun 1.5 VM. It is always there regardless of actual memory usage, and does not indicate that the VM is out of memory.
*** This bug has been marked as a duplicate of 153485 ***
