6137 Unresponsive?

Is anyone else experiencing large periods of unresponsiveness in build 6137?

I've tried it with the supplied JRE and also with JDK 6, but it just seems to keep hanging.

12 comments
Comment actions Permalink

Well, I have noticed that it is slower than the previous eap....
E.g. pressing Ctrl-E takes 2-3 sec. to open the window, this was almost instant before...


BTJ

0
Comment actions Permalink

I've had to revert back to 6117 for the time being, the latest build is currently unusable.

I've no idea whether it's just my system though, so I've raised an issue in JIRA IDEA-10753.

0
Comment actions Permalink

I did, and garbage collection does not seem to be responsible. Also the cpu consumption is low, but the IDE stops working for seconds. I'm reverting to 6117 as well.

0
Comment actions Permalink

Prior to 6137 Ctrl+E took up to 5 seconds for me, the unaddressed issue IDEADEV-11898.
With 6137 Ctrl+E now takes up to 10 seconds.

0
Comment actions Permalink

That's the same scenario as me - the CPU is idling, but the IDE is completely unresponsive.

0
Comment actions Permalink

Agreed. 6137 is unusable. It's VERY unresponsive.


"Simon Knott" <no_reply@jetbrains.com> wrote in message
news:25395458.1166109544594.JavaMail.itn@is.intellij.net...

That's the same scenario as me - the CPU is idling, but the IDE is
completely unresponsive.



0
Comment actions Permalink

+1

That's the same scenario as me - the CPU is idling, but the IDE is
completely unresponsive.



0
Comment actions Permalink

Me too. In particular the startup just hangs there -- it takes 10 minutes to start in my system with nothing else running. No CPU no I/O go figure
:(

0
Comment actions Permalink

It was something like this when I setup idea to start from .bat to use non default JDK. Cause it was some problems with JDK 6.0

0
Comment actions Permalink

Same here. I've rolled back to 6117 due to this....first rollback I can remember having to do during the EAP. I pray that JetBrains fixes the issue and doesn't put out a 6.0.3 release that is going to alienate folks more than 6.0.x already has on performance.

0
Comment actions Permalink

It looks like the JIRA item's been marked as fixed, so fingers crossed :)

0

Please sign in to leave a comment.