-
Bug
-
Resolution: Incomplete
-
P4
-
None
-
7u79
-
x86
-
other
FULL PRODUCT VERSION :
# JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode linux-amd64 compressed oops)
A DESCRIPTION OF THE PROBLEM :
The problem described in https://bugs.openjdk.java.net/browse/JDK-8144565 occurs rarely in 1.7.0_79-b15 .
https://bugs.openjdk.java.net/browse/JDK-8144565 was closed as a duplicate of 6997311
Three reasons while I think that issue is not a dupe and should be re-opened:
* 6997311 is much older and is supposedly fixed in the version that the problem is reported with in 8144565.
* 6997311 is fixed in 1.7.0_79-b15 where I see the issue.
* 6997311 was a SIGFPE, 8144565 is a SIGSEGV .
I see the issue occur in code which concatenates a string with a primitive long. So the compiler will be doing a StringBuffer.append(long) in this instance rather than a toString() as in 8144565 , but both methods call through to getChars which can fail.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
It's super-rare. Unable to reproduce.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
See https://bugs.openjdk.java.net/browse/JDK-8144565
REPRODUCIBILITY :
This bug can be reproduced rarely.
# JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode linux-amd64 compressed oops)
A DESCRIPTION OF THE PROBLEM :
The problem described in https://bugs.openjdk.java.net/browse/JDK-8144565 occurs rarely in 1.7.0_79-b15 .
https://bugs.openjdk.java.net/browse/JDK-8144565 was closed as a duplicate of 6997311
Three reasons while I think that issue is not a dupe and should be re-opened:
* 6997311 is much older and is supposedly fixed in the version that the problem is reported with in 8144565.
* 6997311 is fixed in 1.7.0_79-b15 where I see the issue.
* 6997311 was a SIGFPE, 8144565 is a SIGSEGV .
I see the issue occur in code which concatenates a string with a primitive long. So the compiler will be doing a StringBuffer.append(long) in this instance rather than a toString() as in 8144565 , but both methods call through to getChars which can fail.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
It's super-rare. Unable to reproduce.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
See https://bugs.openjdk.java.net/browse/JDK-8144565
REPRODUCIBILITY :
This bug can be reproduced rarely.