CODEWITHSUNDEEP
javacrashjvm
Adam
Adam

Reputation: 53

Why does the Java VM update 25 crash with internal error

Since Java update 25 the VM crashes occasionally with internal error. With previous versions <25 it was working fine. According to the release notes, the hotspot compiler was modified in update 25. Does it produce defect code that causes the crash? It does not crash if the JIT compiler is turned off with -Xint. I filed a bug here https://bugs.java.com/bugdatabase/view_bug?bug_id=7054478 .

How do I interpret the log file to find out where the crash occurs. I am not able to identify the lines in my Java code where it happenes.

Upvotes: 3

Views: 914

Answers (2)

Stephen C
Stephen C

Reputation: 719376

I searched the Bug Database for the string "Unexpected result from topLevelExceptionFilter", and there were three other hits. They all seem to be about unexpected exceptions in native code propagating back across the JNI boundary.

Is that clue relevant to your application?

Upvotes: 2

Thorbj&#248;rn Ravn Andersen
Thorbj&#248;rn Ravn Andersen

Reputation: 75406

The reason is that an internal assertion failed - the JVM was not in the state it expected to be. This is a good thing because it avoids propagating errors, but a bad thing because it doesn't tell you how to get around it.

If simple tricks like -client or -server doesn't help, then consider a different JVM.

This will allow you to work while Oracle has a look at your bug. It is low priority though, so it make take a while.

Upvotes: 1

Related Questions