IDE hangs so often, it is almost unusable. Any Ideas?

I'm editing a large grails app.  Regularly (perhaps every 5-10 minutes the IDE hangs while I am editing.  It hangs for about 2-4 minutes.  It makes it almost unusable.  I'm now resorting to using textpad for much of my editing.  What gives?  I'm on a windows computer with tons of memory and dual processors.

I've turned off most of the syntax highlighting stuff.  I have no clue what causes it to hang.  Perhaps it is garbage collecting.  Perhaps there is some other background processing killing it.  The Windows Task manager shows the processor pretty busy.  I know it isn't anything else on the computer.  This happens even when I have the grails server turned off.  So it isn't the server trying to restart.

My settings in the ...vmoptions file are

-Xms300m
-Xmx1024m
-XX:MaxPermSize=512m
-ea

6 comments
Comment actions Permalink

Please take a CPU snapshot (http://www.jetbrains.net/devnet/docs/1087).

Thanks,
Anton Makeev

0
Comment actions Permalink

Try the 9.0.1 EAP too.. That build is significantly faster for me:
http://www.jetbrains.net/confluence/display/IDEADEV/Maia+EAP


"Andrew Ressler" <no_reply@jetbrains.com> wrote in message
news:32548456.125171261869866694.JavaMail.clearspace@app8.labs.intellij.net...

I'm editing a large grails app.  Regularly (perhaps every 5-10 minutes the
IDE hangs while I am editing.  It hangs for about 2-4 minutes.  It makes
it almost unusable.  I'm now resorting to using textpad for much of my
editing.  What gives?  I'm on a windows computer with tons of memory and
dual processors.

>

I've turned off most of the syntax highlighting stuff.  I have no clue
what causes it to hang.  Perhaps it is garbage collecting.  Perhaps there
is some other background processing killing it.  The Windows Task manager
shows the processor pretty busy.  I know it isn't anything else on the
computer.  This happens even when I have the grails server turned off.  So
it isn't the server trying to restart.

>

My settings in the ...vmoptions file are
-Xms300m
-Xmx1024m
-XX:MaxPermSize=512m
-ea

>

---
Original message URL:
http://www.jetbrains.net/devnet/message/5253248#5253248


0
Comment actions Permalink

Drat.  I took the suggestion of upgrading to the latest release and I'm back to another worse problem.

My grails app starts up outside of the IDE in about 20-30 seconds.  Now it takes 10-15 minutes when launched from inside of the IDE.

This isn't the first time I've had this problem.  Two minor versions of the IDE (90.162) ago it had this same problem.  Then I upgraded and it started behaving OK.  Now I upgraded to your latest this afternoon and it's back to the same problem of taking forever for the server to come up.  So now the IDE is unusable for debugging.

I've deleted all the cached classes and anything other cached settings I can think of and I'm still having this problem.  I rebooted the server and it has no effect.

I'm really disappointed in this product at this point.  I've never had any other IDE have this many problems with performance.  I want to be helpful and get these problems solved but I am very frustrated right now.

Can I chat with someone in person about this problem?

0
Comment actions Permalink

Do you have any method breakpoints or watchpoints set?
Is it faster if you only run, rather than debug the app from within IDEA?

Andrew Ressler wrote:

Drat.  I took the suggestion of upgrading to the latest release and I'm back to another worse problem.

My grails app starts up outside of the IDE in about 20-30 seconds.  Now it takes 10-15 minutes when launched from inside of the IDE.

This isn't the first time I've had this problem.  Two minor versions of the IDE (90.162) ago it had this same problem.  Then I upgraded and it started behaving OK.  Now I upgraded to your latest this afternoon and it's back to the same problem of taking forever for the server to come up.  So now the IDE is unusable for debugging.

I've deleted all the cached classes and anything other cached settings I can think of and I'm still having this problem.  I rebooted the server and it has no effect.

I'm really disappointed in this product at this point.  I've never had any other IDE have this many problems with performance.  I want to be helpful and get these problems solved but I am very frustrated right now.

Can I chat with someone in person about this problem?

---
Original message URL: http://www.jetbrains.net/devnet/message/5253339#5253339

0
Comment actions Permalink

I have more information.

If I use the exact command string shown from the IDE in a command window, but I leave out the -agentlib option to hook it up to the debugger then it starts up normally (20 seconds or so).  So that points the finger at something that is happening when the IDE is trying to communicate with it.

I looked and I had 7 breakpoints set.  None of them were to be triggered as the server initializes.

Then I removed the 7 breakpoints and it started up just fine.

So is there a bug in your breakpoint logic?  Is this a lesson that one cannot have breakpoints preset before they start the server?  This certainly makes debugging more painful.  I didn't track which files were breakpointed so I don't know if I can easily recreate the exact problem.

If it happens again, I know what to look for and I might be able to give you more information about the nature of the breakpoints.

Andrew

0
Comment actions Permalink

I don't think that it's IDEA's fault (though I am not really sure).
It's simply that method breakpoints and watchpoints slow down the whole VM tremendously.
If you have regular line breakpoints set, that should not affect the speed much.

Andrew Ressler wrote:

I have more information.

If I use the exact command string shown from the IDE in a command window, but I leave out the -agentlib option to hook it up to the debugger then it starts up normally (20 seconds or so).  So that points the finger at something that is happening when the IDE is trying to communicate with it.

I looked and I had 7 breakpoints set.  None of them were to be triggered as the server initializes.

Then I removed the 7 breakpoints and it started up just fine.

So is there a bug in your breakpoint logic?  Is this a lesson that one cannot have breakpoints preset before they start the server?  This certainly makes debugging more painful.  I didn't track which files were breakpointed so I don't know if I can easily recreate the exact problem.

If it happens again, I know what to look for and I might be able to give you more information about the nature of the breakpoints.

Andrew

---
Original message URL: http://www.jetbrains.net/devnet/message/5253347#5253347

0

Please sign in to leave a comment.