Community
Participate
Working Groups
3.2 RC4 Running a plain Eclipse 3.2RC4 (i.e. no WTP or other Callisto projects are installed) on a JDK 1.5.0 VM, I'm often getting OutOfMemoryErrors due to no perm gen space left. Running the same Eclipse install under a JDK 6 VM, I took a VM thread dump, and it looks like the perm gen space is 99% full: Heap def new generation total 11392K, used 206K [0x100a0000, 0x10cf0000, 0x11450000) eden space 10176K, 2% used [0x100a0000, 0x100d38c0, 0x10a90000) from space 1216K, 0% used [0x10a90000, 0x10a90000, 0x10bc0000) to space 1216K, 0% used [0x10bc0000, 0x10bc0000, 0x10cf0000) tenured generation total 150568K, used 65783K [0x11450000, 0x1a75a000, 0x200a0000) the space 150568K, 43% used [0x11450000, 0x1548dfb8, 0x1548e000, 0x1a75a000) compacting perm gen total 55040K, used 54972K [0x200a0000, 0x23660000, 0x240a0000) the space 55040K, 99% used [0x200a0000, 0x2364f3f8, 0x2364f400, 0x23660000) No shared spaces configured.
Also note that I didn't use Ant during the session when I got the OutOfMemoryError.
It looks like I'm running into http://bugs.sun.com/bugdatabase/view_bug.do;:WuuT?bug_id=4957990. Shouldn't we change the default MaxPermSize to 128M (i.e. -XX:MaxPermSize=128m) as we do for the MaxHeapSize ? Otherwise I suspect a lot of people using Callisto will run into this problem as you get much more class loading now.
Sounds like it should at least be a readme. We have to be careful with adding -X options to eclipse.ini because they may not be supported by all VMs.
Actually looks like a dup. *** This bug has been marked as a duplicate of 92250 ***