-
Bug
-
Resolution: Duplicate
-
P2
-
None
-
7u40
-
generic
-
other
See BugDB # 17315456 for detail.
When running java version "1.7.0_17" on OS/X and running jmx enabled cache
server in active persistence mode, causes SIGSEGV in DefaultCacheServer when
connecting from jconsole.
.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000105dab34c, pid=3839, tid=93187
#
# JRE version: 7.0_17-b02
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode bsd-amd64
compressed oops)
# Problematic frame:
# C [libjava.dylib+0x934c] JNU_NewStringPlatform+0x1c8
COUNTER INDICATORS:
TRIGGERS:
Attaching to a JMX process via jconsole will cause the crash. Attaching via JMC also
shows the the coherence process aborting.
KNOWN WORKAROUND: N/A
PRESENT SINCE: Seems to be an issue in the jdk7u port of Mac OSX
HOW TO VERIFY:
NOTES FOR SE: A testcase is available via BugDB report. I'm seeing some other issues while trying to reproduce the SEGV :
java(417,0x19fdef000) malloc: *** error for object 0x19fdde430: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
cache-server.sh: line 22: 417 Abort trap: 6 $JAVA_HOME/bin/java
There are similar reports of JNI network exception crash/issue already in JIRA.
When running java version "1.7.0_17" on OS/X and running jmx enabled cache
server in active persistence mode, causes SIGSEGV in DefaultCacheServer when
connecting from jconsole.
.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000105dab34c, pid=3839, tid=93187
#
# JRE version: 7.0_17-b02
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode bsd-amd64
compressed oops)
# Problematic frame:
# C [libjava.dylib+0x934c] JNU_NewStringPlatform+0x1c8
COUNTER INDICATORS:
TRIGGERS:
Attaching to a JMX process via jconsole will cause the crash. Attaching via JMC also
shows the the coherence process aborting.
KNOWN WORKAROUND: N/A
PRESENT SINCE: Seems to be an issue in the jdk7u port of Mac OSX
HOW TO VERIFY:
NOTES FOR SE: A testcase is available via BugDB report. I'm seeing some other issues while trying to reproduce the SEGV :
java(417,0x19fdef000) malloc: *** error for object 0x19fdde430: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
cache-server.sh: line 22: 417 Abort trap: 6 $JAVA_HOME/bin/java
There are similar reports of JNI network exception crash/issue already in JIRA.
- duplicates
-
JDK-8035897 Better memory allocation for file descriptors greater than 1024 on macosx
- Closed