Out of memory error

Happens on almost all v6.0 EAPs. If I leave my project open over night, I got this in the morning. Also today happened while I was closing my project (already 190M occupied, I though that closing the project will solve it). After I close it (I think I closed it as I received an error, but the interface behave like no project was open), the memory usage remained at 190M of 190M.

I know you need more details on this. How can I do a memory dump / stack trace / whatever ?

6 comments

Hello Alexander,

Happens on almost all v6.0 EAPs. If I leave my project open over
night, I got this in the morning. Also today happened while I was
closing my project (already 190M occupied, I though that closing the
project will solve it). After I close it (I think I closed it as I
received an error, but the interface behave like no project was open),
the memory usage remained at 190M of 190M.

I know you need more details on this. How can I do a memory dump /
stack trace / whatever ?


You could add -XX:+HeapDumpOnOutOfMemoryError to "idea.exe.vmoptions".
My #5734 EAP seems to run on 1.5.0_u8, so this should work.


0

Nope, that didn't do anything (not even in the log). By the way, the log is full of these:

2006-09-25 20:43:13,184 ERROR - #ProblemManager - IntelliJ IDEA 6.0 Release Candidate Build #5734
2006-09-25 20:43:13,184 ERROR - #ProblemManager - JDK: 1.5.0_08
2006-09-25 20:43:13,184 ERROR - #ProblemManager - VM: Java HotSpot(TM) Client VM
2006-09-25 20:43:13,184 ERROR - #ProblemManager - Vendor: Sun Microsystems Inc.
2006-09-25 20:43:13,199 ERROR - #ProblemManager - OS: Windows XP
2006-09-25 20:43:13,199 ERROR - #ProblemManager - Last Action: EditorCopy
2006-09-25 20:43:13,403 INFO - impl.local.LocalFileSystemImpl - Executing request:com.intellij.openapi.vfs.impl.local.LocalFileSystemImpl$4@181ddd
2006-09-25 20:43:40,763 ERROR - #ProblemManager -
java.lang.OutOfMemoryError: Java heap space

repeating at the end.

Can a developer shed light into this? I mean it happens all the time.

0

Hello Alexander,

Nope, that didn't do anything (not even in the log). By the way, the
log is full of these:



That's a pity. If I trigger IDEA into an OOM with above option set (which
was included from 1.5 update 7), I end up with snapshot files named like
"java_pidXXXX.hprof" in my IDEA bin directory.


repeating at the end.

Can a developer shed light into this? I mean it happens all the time.


One other thing you could try is download an EAP build of Yourkit and attach
that. Then, either:
1) Take a snapshot when things seem to be filling up, or
2) Configure YK to take one on "near OOM" condidions
3) Configure YK for periodical snapshots

Hopefully one of these will help.

Regards,

Taras


0

Sorry, I didn't saw that. So I got a 200+ megs file. How do I analyze it? I guess sending it by mail is out of the question.
Don't you have this problem? Leaving IntelliJ open over night with an average sized project should trigger it.

0

Hello Alexander,

Sorry, I didn't saw that. So I got a 200+ megs file. How do I analyze
it? I guess sending it by mail is out of the question.


There are a number of ways to analyze hprof files:
1) Using the "jhat" tool bundled with jdk6
2) Import it into Yourkit for a regular GUI
3) ??? (I'm interested in what others use)

You can zip it and upload to the incoming directory on the Jetbrains server:
ftp://ftp.intellij.net/.uploads

Be sure to give it an unique name, and create a JIRA issue that refers to it.


Don't you have this problem? Leaving IntelliJ open over night with an
average sized project should trigger it.


I usually turn the workstation off.


0

Done. Sorry for the delay. I've been pretty busy these days.
Memory dump (astrotzky_oom_error_memory_dump_java_pid8332.hprof) uploaded and created a JIRA issue (IDEA-9648)[/url].
Hope this helps.

0

Please sign in to leave a comment.