out of memory error dialogs with 5557

I have seen at least two out of memory error dialogs since upgrading to 5557. A coworker of mine has seen a few of these too. He has his max mem set to 512 and I have mine set to 384. I also have my max perm size set to 128.

Any ideas?

9 comments
Comment actions Permalink

Hello Jason,

More details on this problem will help greatly. At least, what operations
you've been performing when the error occured?
It's also will be great if you take a memory snapshot when memory usage indicator
in status bar shows almost full.

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I have seen at least two out of memory error dialogs since upgrading
to 5557. A coworker of mine has seen a few of these too. He has his
max mem set to 512 and I have mine set to 384. I also have my max
perm size set to 128.

Any ideas?



0
Comment actions Permalink

Jason,

You can also add -XX:+HeapDumpOnOutOfMemoryError vm option if you're
using 1.5.0_07 JRE, compress the heap dump file with 7Zip and upload it
to our FTP for analysis.

0
Comment actions Permalink

Ok, I added -XX:+HeapDumpOnOutOfMemoryError to the vmoptions and now I have a couple of heap dump files to upload to you guys. Can you send me the ftp server information?

0
Comment actions Permalink

This still happens in 5561. It appears to be related to Perforce operations. My coworker and I both are seeing the memory shoot up when we cause Idea to open a file for edit from Perforce.

0
Comment actions Permalink

I uploaded the heap dumps. They are named java_pid1620.7z and java_pid3372.7z.

Let me know if you need any more info. Should I file a bug in Tracker about this?

0
Comment actions Permalink

Hello Jason,

JB> I uploaded the heap dumps. They are named java_pid1620.7z and
JB> java_pid3372.7z.
JB>
JB> Let me know if you need any more info. Should I file a bug in
JB> Tracker about this?

I've started looking at this already, but it'll be best if you file a request,
so that its resolution can be tracked.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hello Jason,

JB> I uploaded the heap dumps. They are named java_pid1620.7z and
JB> java_pid3372.7z.
JB>
JB> Let me know if you need any more info. Should I file a bug in
JB> Tracker about this?

Fixed. The problem was not a memory leak, but rather an infinite loop when
parsing the Perforce view specification.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Dmitry,

Good to hear! I look forward to the next EAP! Thanks much.

-Jason

0

Please sign in to leave a comment.