We are using IntelliJ 6.0.1 (build 5784) which is frequently running out of memory despite having reasonable memory settings. Here are our idea.vmoptions:
System is Linux 2.6 running Sun JDK 1.5.0_09 and has about 1G of free memory out of 2G total. I've tried playing around with both mx and MaxPermSize but eventually IntelliJ still crashes with the following message:
Exception in thread "CompilerThread0" java.lang.OutOfMemoryError: requested 268435464 bytes for Chunk::new. Out of swap space?
This seems like some thread is trying to allocate an awful lot of memory. Is this a known issue with a possible workaround?
Please sign in to leave a comment.
Try the 6.0.2 EAP version 6043
Maybe it's solved there...
Perhaps full rebuild will help - such big value may be because of corrupt caches.
"Develop with pleasure!"
"David Connelly" <firstname.lastname@example.org> wrote in message news:26887357.1161392878314.JavaMail.email@example.com...
We are still hitting this problem with 6.0.2. I think reverting back to 6.0 may have helped, but I am rebuilding my cache at least once a day and eventually after a few hours IJ produces the same error:
Exception in thread "CompilerThread1" java.lang.OutOfMemoryError: requested 268435464 bytes for Chunk::new. Out of swap space?
I am not the only one encountering this problem, another coworker of mine is getting the same exception, and the amount of memory it tries allocating is always the same. This even occurs while IJ is sitting idle.
Depending on what functionality of IDEA you use, a MaxPerm size of 92m can be fairly small. My installation used to run out of PermSpace a lot, but seems to run fine now at 148m.
There's another possibility that the free memory on your machine is extremely fragmented, i.e. even though there's 1GB free, the size of the contiguous memory is too low to create the requested block. Although it seems a bit strange that the HotSpot compiler wants to allocate 256m at once.
See also http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4916142 which describes a similar error and seems to provide a workaround: The VM-options -XX:+UseDefaultStackSize -Xss256K