Anyone else having frequent HotSpot crashes in Selena?

Since upgrading to Selena (both 6667 and 7000) I've been getting
frequent HotSpot crashes (IDEA suddenly disappears and leaves a
hs_err.pid file behind). Is anyone else experiencing this?

I recently tried reverting to using Java 1.5.0_08, which was supplied
with earlier versions of IDEA, instead of 1.5.0_10 which is supplied
with the newer versions, but that seems to have had no effect on the
frequency of the crashes.

6.0.4 used to be stable. I have not yet tried to go back to that
version, since I'm not sure whether the project files are stable, but I
guess that is the next thing to try.

The computer seems to be stable except for these crashes. I'm running
Windows XP with the latest fixes, on a 1.8 GHz P4 machine with 1 GB of
memory. I might try a memtest86 run tonight to be sure there aren't
memory issues, but that seems to be an unlikely cause given that it
appears to crash in the same place every time.

I realize that HotSpot crashes generally aren't something you can affect
from within Java, but I'm attaching a few of the crash logs in case
anyone here can help identify the problem or suggest a workaround.


Attachment not added (too many attachments): "hs_err_pid3112.log"



Attachment(s):
hs_err_pid872.log
hs_err_pid3844.log
hs_err_pid3168.log
hs_err_pid164.log
hs_err_pid344.log
4 comments
Comment actions Permalink

I'm afraid I haven't had any hotspot crashes, with normal use, with either of the last two Selena builds, it's been rock solid.

However, I have noticed that IDEA will completely die if you use multiple monitors and change the number you are using while IDEA is open (both IDEA 6 and Selena do this). I believe this is a JVM crash, although I haven't bothered looking into it too heavily.

0
Comment actions Permalink

Hello Simon,

However, I have noticed that IDEA will completely die if you use
multiple monitors and change the number you are using while IDEA is
open (both IDEA 6 and Selena do this). I believe this is a JVM crash,
although I haven't bothered looking into it too heavily.


This is a very, very well known Swing issue.

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


0
Comment actions Permalink

No vm crashes for me. But apparently these kinds of crashes can also be
caused by third party software:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6205768

Why do you need JAVA_HOME=c:\programs\j2sdk1.4.2_01 ?

C:\Program Files\AceClockXP\Mouse_dll.dll and C:\WINNT\TEMP\IadHide4.dll
appear in the logs. One of those might be the cause, especially if you
installed them recently.

Bas

Jonas Kvarnström wrote:

Since upgrading to Selena (both 6667 and 7000) I've been getting
frequent HotSpot crashes (IDEA suddenly disappears and leaves a
hs_err.pid file behind). Is anyone else experiencing this?

I recently tried reverting to using Java 1.5.0_08, which was supplied
with earlier versions of IDEA, instead of 1.5.0_10 which is supplied
with the newer versions, but that seems to have had no effect on the
frequency of the crashes.

6.0.4 used to be stable. I have not yet tried to go back to that
version, since I'm not sure whether the project files are stable, but I
guess that is the next thing to try.

The computer seems to be stable except for these crashes. I'm running
Windows XP with the latest fixes, on a 1.8 GHz P4 machine with 1 GB of
memory. I might try a memtest86 run tonight to be sure there aren't
memory issues, but that seems to be an unlikely cause given that it
appears to crash in the same place every time.

I realize that HotSpot crashes generally aren't something you can affect
from within Java, but I'm attaching a few of the crash logs in case
anyone here can help identify the problem or suggest a workaround.

0
Comment actions Permalink

Why do you need JAVA_HOME=c:\programs\j2sdk1.4.2_01 ?


I noticed that too. It's just a remainder from when I ran software that
required JAVA_HOME to be set; the directory no longer exists.

C:\Program Files\AceClockXP\Mouse_dll.dll and C:\WINNT\TEMP\IadHide4.dll
appear in the logs. One of those might be the cause, especially if you
installed them recently.


I did install AceClock very recently, since I wanted the taskbar to
auto-hide but still wanted to see the current time on screen. I guess
it didn't occur to me that this could affect a completely different
process, but I'll try uninstalling it and checking whether it has any
effect.

It seems that iadhide4.dll has to do with the F-Secure Backweb process
which has been installed for years so that is probably not the cause. I
can't imagine why it would be in c:\winnt\temp, though.

0

Please sign in to leave a comment.