Introduction

Java JVM crashes with SIGBUS signal when unaligned memory access occurs in native code. This guide provides step-by-step diagnosis and resolution with specific commands and code examples.

Symptoms

Typical symptoms and error messages when this issue occurs:

bash
# A fatal error has been detected by the Java Runtime Environment:
#  SIGBUS (0xa) at pc=0x00007f8b2c1a4e2d, pid=12345, tid=12346
# Problematic frame:
# C  [libnio.so+0x4e2d]

Observable indicators: - Application logs show errors or exceptions - JVM crashes or becomes unresponsive - Related services may fail or timeout

Common Causes

  1. 1.JVM crashes are typically caused by:
  2. 2.Native memory access violations in JNI code
  3. 3.JVM bugs in specific versions
  4. 4.Hardware failures or memory corruption
  5. 5.Incompatible native libraries

Step-by-Step Fix

Step 1: Check Current State

bash
java -version

Step 2: Identify Root Cause

bash
jcmd <pid> VM.info

Step 3: Apply Primary Fix

java
// Primary fix: update configuration
@Configuration
public class AppConfig {
    @Bean
    public MyBean myBean() {
        MyBean bean = new MyBean();
        bean.setTimeout(30000);
        return bean;
    }
}

Apply this configuration and restart the application.

Step 4: Apply Alternative Fix (If Needed)

java
// Alternative fix: use properties
# application.properties
app.timeout=30000
app.retry-count=3
app.enabled=true

Monitor JVM metrics after changes using JConsole or VisualVM.

Step 5: Verify the Fix

After applying the fix, verify with:

bash
jcmd <pid> VM.info && jstat -gc <pid> 1s 5

Expected output should show successful operation without errors.

Common Pitfalls

  • Setting Xms larger than Xmx
  • Ignoring JVM crash logs
  • Not tuning GC for workload type

Best Practices

  • Use G1GC for heaps > 4GB
  • Set Xms equal to Xmx for production
  • Monitor GC logs continuously
  • Java OutOfMemoryError Heap Space
  • Java GC Overhead Limit Exceeded
  • Java JVM Crash Signal Error