Build 1089 severe memory leak

After editing few files of code and running CVS update/commit the memory usage doesn't get down anymore.

I'm running with option -server -Xms64m -Xmx64m and the idea memory indicator is (right now at 56M) and it doesn't decrease no matter how many times I hit the manual gc button.

The 'on the fly' parser is slow as h**l also. The build 1080 was like a rocket compared to this build.

Anyone else experiencing this behaviour?

10 comments

Hezekiel wrote:

After editing few files of code and running CVS update/commit the memory usage doesn't get down anymore.

I'm running with option -server -Xms64m -Xmx64m and the idea memory indicator is (right now at 56M) and it doesn't decrease no matter how many times I hit the manual gc button.

The 'on the fly' parser is slow as h**l also. The build 1080 was like a rocket compared to this build.

Anyone else experiencing this behaviour?


YEs on all counts, I filed a but about the parser slowing down, I've
gotten IDEA to hang twice on paste, and in fact the memory goes up and
up and up, and never comes back down. I had about 240MB of RAM at one
point with about 10 files in my project, and only 1 open, and debugging
running.

1089 is definitely a regression.

R

0

The leak probably comes from the debugger, and I've seen it long before
1089.
Eugene.

YEs on all counts, I filed a but about the parser slowing down, I've
gotten IDEA to hang twice on paste, and in fact the memory goes up and
up and up, and never comes back down. I had about 240MB of RAM at one
point with about 10 files in my project, and only 1 open, and debugging
running.

>

1089 is definitely a regression.

>

R



0

Evgueny Vigdorchik wrote:

The leak probably comes from the debugger, and I've seen it long before
1089.
Eugene.


Heh, then maybe I'm seeing it now because I can actually work in the EAP
for long periods of time :)

hopefuly you guys will run some analysis on this sucker and get it
fixed... that's a wholelotta ram!

R

>>YEs on all counts, I filed a but about the parser slowing down, I've
>>gotten IDEA to hang twice on paste, and in fact the memory goes up and
>>up and up, and never comes back down. I had about 240MB of RAM at one
>>point with about 10 files in my project, and only 1 open, and debugging
>>running.
>>
>>1089 is definitely a regression.
>>
>>R


0

Could you, please, provide more information, when on the fly parser slows
down - on which file types, what is file's and project size, etc.

Best regards,

Sergey Dmitriev.

-



JetBrains Inc.

http://www.intellij.com

"Develop with pleasure!"

-



"Robert S. Sfeir" <robert@codepuccino.com> wrote in message
news:btu4pk$f2$1@is.intellij.net...

Hezekiel wrote:

After editing few files of code and running CVS update/commit the memory

usage doesn't get down anymore.

>

I'm running with option -server -Xms64m -Xmx64m and the idea memory

indicator is (right now at 56M) and it doesn't decrease no matter how many
times I hit the manual gc button.

>

The 'on the fly' parser is slow as h**l also. The build 1080 was like a

rocket compared to this build.

>

Anyone else experiencing this behaviour?

>

YEs on all counts, I filed a but about the parser slowing down, I've
gotten IDEA to hang twice on paste, and in fact the memory goes up and
up and up, and never comes back down. I had about 240MB of RAM at one
point with about 10 files in my project, and only 1 open, and debugging
running.

>

1089 is definitely a regression.

>

R



0

Sergey Dmitriev (JetBrains) wrote:

Could you, please, provide more information, when on the fly parser slows
down - on which file types, what is file's and project size, etc.


I filed a bug for this. The slowdown that I've seen seems to only be in
java and jsp files that use scriptlets.

It's pretty noticeable.

R

0

Could you, please, provide more information, when on
the fly parser slows
down - on which file types, what is file's and
project size, etc.


Update:
In my case the culprit was probably the indexing phase. The slowdown occurred during the 'first run' of 1089 during which the project and the JRE got indexed.

After restart the problem was much less noticeable or non existent. I'll post more information tomorrow after I've worked at least 6 hours on the project.

0

Update:

On build 1094:
Just by doing lot's of makes and compiles to the project and viewing all settings windows the memory usage slowly increases and when gc'd doesn't get back to original readings.

0

Memory usage will increase after first compilation, and when working with
CVS after (first) update/commit project/open FileView.
Please, describe steps to waste memory if you know.

--

Dmitry Peshehonov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


"Hezekiel" <tilaus@almasoftware.com> wrote in message
news:29250150.1074006455010.JavaMail.itn@is.intellij.net...

Update:

>

On build 1094:
Just by doing lot's of makes and compiles to the project and viewing all

settings windows the memory usage slowly increases and when gc'd doesn't get
back to original readings.


0

D**n! Could be a LAF issue. I was using Tonic LAF. Swithced to IDEA LAF, and the problem seems to be less noticeable..

0

Dmitry Peshehonov (JetBrains) wrote:

Memory usage will increase after first compilation, and when working with
CVS after (first) update/commit project/open FileView.
Please, describe steps to waste memory if you know.


Dmitry,

Just open a JSP, make a change, hit make to copy to exploded directory
of web module, repeat about 100 times, since you don't auto copy JSPs
over to exploded dir. memory will grow and not GC.

R

0

Please sign in to leave a comment.