Crash: SIGSEGV when opening settings from the top title bar

Duplicate Check

• I confirm I searched for existing reports and found no duplicates.

Describe the Bug

App Information

• App name: SimpMusic
• Package name: com.maxrave.simpmusic
• Version: 1.2.1
• Version code: 50
• Issue type: Crash
• Android version: 9.0

Expected Behavior

The app should remain stable when the user taps the Settings icon on the right side of the top title bar.

The settings page should open normally without crashing the app process.

Actual Behavior

The app crashes after the user taps the Settings icon.

The crash is a native segmentation fault on the app main thread. Android force-finishes MainActivity, terminates the app process, and schedules a restart of the app's media playback service.

Crash Log

05-22 11:55:13.041 I/chatty (32507): uid=10112(com.maxrave.simpmusic) expire 110 lines
05-22 11:55:14.049 I/chatty (32507): uid=10112(com.maxrave.simpmusic) identical 110 lines
05-22 11:55:15.057 I/chatty (32507): uid=10112(com.maxrave.simpmusic) identical 110 lines
05-22 11:55:15.706 I/chatty (32507): uid=10112(com.maxrave.simpmusic) identical 70 lines
05-22 11:55:15.816 I/chatty (32507): uid=10112(com.maxrave.simpmusic) identical 11 lines
05-22 11:55:15.849 I/chatty (32507): uid=10112(com.maxrave.simpmusic) identical 1 line
05-22 11:55:16.045 I/chatty (32507): uid=10112(com.maxrave.simpmusic) identical 20 lines
05-22 11:55:17.056 I/chatty (32507): uid=10112(com.maxrave.simpmusic) identical 110 lines
05-22 11:55:18.065 I/chatty (32507): uid=10112(com.maxrave.simpmusic) identical 110 lines
05-22 11:55:19.054 I/chatty (32507): uid=10112(com.maxrave.simpmusic) identical 108 lines
05-22 11:55:19.793 I/chatty (32507): uid=10112(com.maxrave.simpmusic) identical 80 lines
05-22 11:55:19.917 I/chatty (32507): uid=10112(com.maxrave.simpmusic) identical 12 lines
05-22 11:55:19.920 D/MainActivity(32507): Current destination: com.maxrave.simpmusic.ui.navigation.destination.home.AnalyticsDestination
05-22 11:55:19.992 I/chatty (32507): uid=10112(com.maxrave.simpmusic) identical 1 line
05-22 11:55:20.082 F/libc (32507): Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x14 in tid 32507 (xrave.simpmusic), pid 32507 (xrave.simpmusic)
05-22 11:55:20.118 F/DEBUG ( 2435): pid: 32507, tid: 32507, name: xrave.simpmusic  >>> com.maxrave.simpmusic <<<
05-22 11:55:20.120 F/DEBUG ( 2435): #05 pc 00000000000172fc /dev/ashmem/dalvik-/data/app/com.maxrave.simpmusic-PP6FIfhmJt_uvv0QcFjBaw==/oat/arm64/base.art (deleted)
05-22 11:55:20.333 W/ActivityManager( 1609): Force finishing activity com.maxrave.simpmusic/.MainActivity
05-22 11:55:20.343 W/InputDispatcher( 1609): channel 'c2c1d63 com.maxrave.simpmusic/com.maxrave.simpmusic.MainActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
05-22 11:55:20.343 E/InputDispatcher( 1609): channel 'c2c1d63 com.maxrave.simpmusic/com.maxrave.simpmusic.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
05-22 11:55:20.346 I/WindowManager( 1609): WIN DEATH: Window{c2c1d63 u0 com.maxrave.simpmusic/com.maxrave.simpmusic.MainActivity}
05-22 11:55:20.346 W/InputDispatcher( 1609): Attempted to unregister already unregistered input channel 'c2c1d63 com.maxrave.simpmusic/com.maxrave.simpmusic.MainActivity (server)'
05-22 11:55:20.347 I/ActivityManager( 1609): Process com.maxrave.simpmusic (pid 32507) has died: vis +99TOP
05-22 11:55:20.347 W/ActivityManager( 1609): Scheduling restart of crashed service com.maxrave.simpmusic/com.maxrave.media3.service.SimpleMediaService in 1000ms
05-22 11:55:20.350 W/SurfaceFlinger( 1467): Attempting to set client state on removed layer: com.maxrave.simpmusic/com.maxrave.simpmusic.MainActivity#0
05-22 11:55:20.350 W/SurfaceFlinger( 1467): Attempting to destroy on removed layer: com.maxrave.simpmusic/com.maxrave.simpmusic.MainActivity#0

Analysis

The crash is a native segmentation fault:

Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x14

This means the app process attempted to access an invalid memory address. The fault address is very small:

fault addr 0x14

This usually indicates a null or near-null pointer dereference in native/runtime-level code.

The log shows that shortly before the crash, the app reports the current navigation destination as:

Current destination: com.maxrave.simpmusic.ui.navigation.destination.home.AnalyticsDestination

Then the process crashes on the main app thread:

tid 32507 (xrave.simpmusic), pid 32507 (xrave.simpmusic)

The only native frame shown in the provided crash summary points to the ART/oat memory area:

/dev/ashmem/dalvik-/data/app/com.maxrave.simpmusic-PP6FIfhmJt_uvv0QcFjBaw==/oat/arm64/base.art (deleted)

Because the visible trigger is tapping the Settings icon, the crash likely occurs during navigation or UI state transition from the current screen toward the settings-related destination. However, the immediate fatal condition is not a normal Java/Kotlin exception; it is a native memory access violation.

After the segmentation fault, Android force-finishes the foreground activity:

Force finishing activity com.maxrave.simpmusic/.MainActivity
WIN DEATH: Window{c2c1d63 u0 com.maxrave.simpmusic/com.maxrave.simpmusic.MainActivity}
Process com.maxrave.simpmusic (pid 32507) has died

The system also schedules a restart of the app's media playback service:

Scheduling restart of crashed service com.maxrave.simpmusic/com.maxrave.media3.service.SimpleMediaService in 1000ms

This indicates that the crash terminates not only the UI flow but also affects the running media service associated with the app process.

Steps to Reproduce

1. Launch SimpMusic.
2. Stay on the current screen.
3. Tap the Settings icon on the right side of the top title bar.
4. Observe whether the settings page opens successfully.
5. The app crashes with a native SIGSEGV.

Expected Behavior

The app should remain stable when the user taps the Settings icon on the right side of the top title bar.
The settings page should open normally without crashing the app process.

App Version

1.2.1

Android Version

Android 9.0

Device Model

Android 9.0 emulator

Custom ROM

• I am using a custom ROM

Custom ROM Name (if applicable)

No response

Screenshots (optional)

No response

Log / Error Details

No response

Start by reproducing the crash on the Android 9.0 emulator and inspect MainActivity's navigation path from the top title bar Settings icon, especially when the current destination is AnalyticsDestination. Use the provided SIGSEGV log to trace the transition and verify that the settings page opens without terminating MainActivity or the media service.