Opened 10 years ago

Closed 9 years ago

Last modified 6 years ago

#525 closed defect (duplicate)

jvm crash in native code in Windows

Reported by: killyourtv Owned by: walking
Priority: major Milestone: 0.8.12
Component: unspecified Version: 0.8.8
Keywords: Cc:
Parent Tickets: Sensitive: no


Reported by walking on IRC.

<walking> # A fatal error has been detected by the Java Runtime Environment:
<walking> #
<walking> #  Internal Error (safepoint.cpp:635), pid=3184, tid=3588
<walking> #  fatal error: Illegal threadstate encountered: 4
<walking> #
<walking> # JRE version: 6.0_26-b03
<walking> # Java VM: Java HotSpot(TM) Client VM (20.1-b02 mixed mode, sharing windows-x86 )
<walking> # If you would like to submit a bug report, please visit:
<walking> #
<walking> # The crash happened outside the Java Virtual Machine in native code.
<walking> # See problematic frame for where to report the bug.
<walking> #

I have also had this error in the past on an amd64 in Windows, even with 0.8.2, so the jbigi compiles checked-in with 0.8.7 aren't the culprit.


Change History (5)

comment:1 Changed 10 years ago by zzz

Owner: set to walking
Status: newassigned

I don't know of any way that our code could be at fault. It's likely either a JVM bug or a memory glitch.

Reassigning to walking to attach the full crash report, which may provide more clues.

comment:2 Changed 10 years ago by zzz

Resolution: no response
Status: assignedclosed

comment:3 Changed 9 years ago by zzz

Resolution: no response
Status: closedreopened

comment:4 Changed 9 years ago by zzz

Resolution: duplicate
Status: reopenedclosed

dup of #82 which is still open. Sadly, a google search of 'illegal threadstate encountered: 4' returns this ticket as the top entry.

comment:5 Changed 6 years ago by DjJeshk

Maybe we got a bug like this?

This is still happening at 0.9.19

Note: See TracTickets for help on using tickets.