-
Bug
-
Resolution: Cannot Reproduce
-
P4
-
None
-
6u1
-
x86
-
windows_xp
One of CAP member's customer has update the Java VM to 1.6.0_01-b06 from 1.5. Now he has a
crash with the IE
but not with the firefox. That it is a regression in 1.6.0_01-b06.
It is 100% reproducable. Their Java
applet run on thousands computers without this crash.
* Java application is a signed Applet with pure Java. The Signatur is using for file, clipboard
and printer access.
* Yes, it crash only with a single system. We does not know what are the significat difference
is to the other systems. We think it is a timing/thread problem.
* The flag -X:+RestoreMXCSROnJNICall has no effect. See the attach crash dumps.
* Appletviewer work also without a crash.
The crash occur ever on readline() in different classes. The problematic frame is:
~RuntimeStub::resolve_virtual_call
or
~RuntimeStub::resolve_opt_virtual_call
See the attached crash dumps for more details.
This bug seems equals or related to the follow bugs: 6563559, 6539718, 6500626, 6463385
We would like to request that the customer try the latest JDK6 Update 10 Beta code.
We believe this fix for 6550813 also resolves this bug. 6550813 is included in
JDK6 Update 10 Beta.
crash with the IE
but not with the firefox. That it is a regression in 1.6.0_01-b06.
It is 100% reproducable. Their Java
applet run on thousands computers without this crash.
* Java application is a signed Applet with pure Java. The Signatur is using for file, clipboard
and printer access.
* Yes, it crash only with a single system. We does not know what are the significat difference
is to the other systems. We think it is a timing/thread problem.
* The flag -X:+RestoreMXCSROnJNICall has no effect. See the attach crash dumps.
* Appletviewer work also without a crash.
The crash occur ever on readline() in different classes. The problematic frame is:
~RuntimeStub::resolve_virtual_call
or
~RuntimeStub::resolve_opt_virtual_call
See the attached crash dumps for more details.
This bug seems equals or related to the follow bugs: 6563559, 6539718, 6500626, 6463385
We would like to request that the customer try the latest JDK6 Update 10 Beta code.
We believe this fix for 6550813 also resolves this bug. 6550813 is included in
JDK6 Update 10 Beta.