[CASSANDRA-14137] Cassandra crashes on startup. Crash Problematic frame: # C [sigar-amd64-winnt.dll+0x14ed4] using JRE version: Java(TM) SE Runtime Environment (9.0+11)

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 3.0.15, 3.0.16
• Component/s: Legacy/Core, Observability/Metrics

Environment

Cassandra 3.0.15
Java 9.0.1+11
Workaround is to use Java 8

• Severity: Low
• Assignee: Unassigned
• Reporter: mark pettovello
• Created: 26/Dec/17 18:05
• Updated: 16/Apr/19 09:29
• Resolved: 27/Dec/17 02:26

Description

Startup of Cassandra crashes in sigar-amd64-winnt.dll+0x14ed4.
Short term work around: change from Java 9 back to Java 8.

#

1. A fatal error has been detected by the Java Runtime Environment:
   #
2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000010014ed4, pid=7112, tid=1764
   #
3. JRE version: Java(TM) SE Runtime Environment (9.0+11) (build 9.0.1+11)Problematic frame:
4. C [sigar-amd64-winnt.dll+0x14ed4]
5. Java VM: Java HotSpot(TM) 64-Bit Server VM (9.0.1+11, mixed mode, tiered, compressed oops, concurrent mark sweep gc, windows-amd64)
6. Problematic frame:
7. C [sigar-amd64-winnt.dll+0x14ed4]
   #
8. No core dump will be written. Minidumps are not enabled by default on client versions of Windows
   #
9. If you would like to submit a bug report, please visit:
10. http://bugreport.java.com/bugreport/crash.jsp
11. The crash happened outside the Java Virtual Machine in native code.
12. See problematic frame for where to report the bug.

Issue Links

• duplicates: CASSANDRA-9608 Support Java 11