I am using flex builder 3 plugin on top of wtp eclipse 3.2.2. The application is quite heavy and needs 2 GB of physical RAM when running on JBoss.
I have eclipse.ini set with the following options:
Now whenever I am trying to build the project, eclipse crashes with the following error:
# An unexpected error has been detected by Java Runtime Environment:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d88b795, pid=4572, tid=4660
# Java VM: Java HotSpot(TM) Client VM (11.0-b16 mixed mode windows-x86)
# Problematic frame:
# V [jvm.dll+0x8b795]
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp #
--------------- THREAD ---------------
Current thread (0x58412400): VMThread [stack: 0x584a0000,0x584f0000] [id=4660]
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x00385750] UNKNOWN - owner thread: 0x58412400
[0x00385bb0] UNKNOWN - owner thread: 0x59f45000
def new generation total 70976K, used 23241K [0x02a70000, 0x07770000, 0x07a20000)
eden space 63104K, 36% used [0x02a70000, 0x04122770, 0x06810000)
from space 7872K, 0% used [0x06810000, 0x06810000, 0x06fc0000)
to space 7872K, 0% used [0x06fc0000, 0x06fc0000, 0x07770000)
tenured generation total 945280K, used 32043K [0x07a20000, 0x41540000, 0x43670000)
the space 945280K, 3% used [0x07a20000, 0x0996ac98, 0x0996ae00, 0x41540000)
compacting perm gen total 38144K, used 37935K [0x43670000, 0x45bb0000, 0x56270000)
the space 38144K, 99% used [0x43670000, 0x45b7bf00, 0x45b7c000, 0x45bb0000) No shared spaces configured.
After looking at this log, I got the line starting with "compacting perm gen" which made me thinking that there might be some problem in Perm Gen memory. I got quite a few references on the net but none could lead me to concrete solution. I tried with different combination of settings for MaxPermSize but no luck.
has anyone faced this problem on eclipse and aware of any possible solution?
love your job and not your company;
...because you never know when your company will stop loving you!
Also, it is not unusual to see the permgen space 99% occupied. The JVM usually uses only as much permgen space as is required. Note, for example, that you set max permgen size to 300MB but the JVM is using only 38MB.
I noticed that you are using JDK 1.6.0_03. That is a really old JVM. I very highly recommend upgrading to the latest JDK 6! I know, for example, that JVMs older than 1.6.0_04 have issues with JBoss AS 5.0.0.GA, and have serious issues when running on Vista.
Actually I am already using JVM 1.6.0_11-b03. And currently the problem is while running eclipse and could not reach to deployment stage at all so far. One thing I noticed is that I enabled some code styles in the eclipse preferences, and since then I am facing this problem. But now even after reverting those changes, the problem persists.
I have already reported this potential bug to sun and waiting for their response.
subject: JVM crash due to perm gen space 99% in use