-
Bug
-
Resolution: Won't Fix
-
P2
-
6u26
-
generic
-
generic
SHORT SUMMARY:
Java_java_net_SocketOutputStream_socketWrite0() writes beyond the red guard
page causing a sigsegv.
INDICATORS:
crash (to be described in bug desc)
COUNTER INDICATORS:
no crash
TRIGGERS:
jdk 6u26
KNOWN WORKAROUND:
Increasing stacksize and increasing shadowpages showed some success as a
workaround, but the customer continued to see crashes even after increasing
stacksize to 3M and shadowpages to 10. One crash had one thread with a
stacksize of 3M and over 13000 frames in the stack.
PRESENT SINCE:
fcs presumably
HOW TO VERIFY:
run testcase (to be attached)
NOTES FOR SE:
None
REGRESSION:
no info
Java_java_net_SocketOutputStream_socketWrite0() writes beyond the red guard
page causing a sigsegv.
INDICATORS:
crash (to be described in bug desc)
COUNTER INDICATORS:
no crash
TRIGGERS:
jdk 6u26
KNOWN WORKAROUND:
Increasing stacksize and increasing shadowpages showed some success as a
workaround, but the customer continued to see crashes even after increasing
stacksize to 3M and shadowpages to 10. One crash had one thread with a
stacksize of 3M and over 13000 frames in the stack.
PRESENT SINCE:
fcs presumably
HOW TO VERIFY:
run testcase (to be attached)
NOTES FOR SE:
None
REGRESSION:
no info
- relates to
-
JDK-6807602 Increase MAX_BUFFER_LEN and MAX_HEAP_BUFFER_LEN on 64-bit Solaris and Linux
- Resolved
-
JDK-6983989 JVM native socket code uses too much of the stack
- Closed
-
JDK-7059899 Stack overflows in Java code cause 64-bit JVMs to exit due to SIGSEGV
- Closed