Stability
Arghh ]]>. Over the last half year, Intellij became increasingly unstable. Random crashes, 100% CPU usage, bugs, project descriptors that break, slowdowns, and so on. The EAP quality is far from 'stable'. So here's a call to the JetBrains people: test more, code less, increase quality. Give us a stable environment to develop in. It's frustrating enough debugging our own applications. That being said, I realize EAP contains 'early' and Eclipse is even worse compared to Intellij.
请先登录再写评论。
Ah, the monthly performance/stability rant. The most productive thing to do is highlight here exactly what your individual problems are (create issues with cpu snapshots, etc) and encourage others to do so on your thread. JB is pretty responsive when you give them something to work with.
Hello Mathias,
If you like stability, you are very much welcome to use the production release.
All the types of problems that you have listed commonly occur in EAP builds
in every EAP cycle, and are usually addressed fairly quickly. If you can
describe specific problems with the latest EAP build which affect you right
now, we'll be happy to look into them.
--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
Mathias Bogaert wrote:
Hmm, I think the Selena EAP is actually more stable compared to the EAPs of the last two versions -
apart from the more frequent deadlocks, which are the price to pay for better support of multi-core
machines. And after all, it's an EAP. It is supposed to contain some annoyances, and it's the point
of an EAP to get rid of them.
Sascha
I realize I can use the production release, but once you're on the EAP track, there's no way back (unless you setup your project again in the older version, which is not an option to me (crappy GWT compiler support).
The problem I have now is a 100% CPU peak, which seams to occur when memory is fully charged (430MB). Nothing in the logs, nothing reported. The only thing to do is a process kill and wait for a slooow startup since now it starts parsing all libs all over again. I'm running 7111 on Windows XP on a single core CPU (Pentium Mobile 2ghz).
Hello Mathias,
Can you take a CPU snapshot or at least a thread dump?
--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
You might try to adjust memory settings, Sun VM uses 100% cpu when
almost all memory is used.
Mathias Bogaert wrote:
--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"
My idea.exe.vmoptions:
-Xms380m
-Xmx380m
-XX:MaxPermSize=140m
-XX:MaxGCPauseMillis=10
–XX:MaxHeapFreeRatio=70
-XX:+UseConcMarkSweepGC
–XX:+CMSIncrementalPacing
but still locks after about 1 hours of eating code...
No I can't, since my screen 'goes gray' meaning even the Swing redraw thread locks.
Hello Mathias,
You can run idea.bat instead of idea.exe and press Ctrl-Break in the console
to take a thread dump even if the EDT is locked.
Another option is to use the AdaptJ tool: http://www.adaptj.com/root/main/stacktrace
--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
On 2007-08-07 23:12:54 +0400, Mathias Bogaert
<mathias.bogaert@etmint.com> said:
-XX:MaxGCPauseMillis=10
If I understand correctly this means everything CG haven't been able to
collect in 10ms will live until full GC happens. No wonder it happens
soon and takes long this way. Generally, tweaking VM GC options doesn't
always change things to better. Try running with default options
instead (setting -Xmx to higher value may make sense if your project is
really large).
Or "jstack" if you're running IDEA on Java 6 (Java 5 requires -Dcom.sun.management.jmxremote JVM option).
Btw, Dimtry, IDEA process displayed without name in either "jconsole" or "jps", see the images attached - those are IDEA processes
Attachment(s):
1.png
2.png
The deadlocks are intensely annoying and make me want to lash out wildly at the nearest thing. There's something incredibly frustrating about having idea lock up on an 8 core machine with 0% cpu usage.
Though even more irritating is the incredibly obnoxious memory popup dialog. Is there any chance for the default memory allocation on OSX to be upped to 256mb or so? I doubt anyone has a machine with less than 1gb these days.
Hello Hani,
Any thread dumps?
--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
Here is mine.
Attachment(s):
ideathreaddump
Hello Mathias,
This is not a deadlock - the operation will eventually complete.
http://www.jetbrains.net/jira/browse/IDEADEV-20057
--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
Thank you, what is used IDEA build number?
Mathias Bogaert wrote:
--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"
Thanks. Build is 7118. Env.: Windows XP, JDK 6u2. I cleaned up the system dir before launching Idea.
What I do to counter that is make sure I have 1 or 2 previous EAP releases. There are always issues with EAP's (that would be ANYONE's EAP's, not just JetBrain's), like with 7111 on a Mac had a completely broken CVS support, couldn't even log in to the CVS server, so I just went back to using build 7096. Yes, it was much less responsive than 7111, but it was a solution. If you want production level stability, the only answer is to use a production release.
I am actually amazed at how useable the Idea EAP's are. I've been a JetBrains customer for several years now, and I think that over that time I've used the EAP releases for production work about 70% of the time. Can't say anything close to that for any other product I know of.
The garbage collector eats the cpu as memory reaches the limit.
Raise your maximum vm heap size Xmx setting. It could be the EAP
has some memory leaks, and so the memory is growing over time and
once it gets close to the limit, performance degrades.
I have had this happen myself on my machine Windows XP SP2 with
the Selena EAPs. I just closed/kill IDEA, bump up the memory, and
restart.