SIGSEGV in rive::ImageAsset::renderImage — native crash heavily concentrated on Android 16 #440
Description
Description
We're experiencing a native SIGSEGV crash in rive::ImageAsset::renderImage affecting a significant number of users in production. The crash is ongoing on Rive Android 11.1.2 with RendererType.Rive.
Stacktrace
SIGSEGV: Segfault
at ()
at Java_app_rive_runtime_kotlin_core_ImageAsset_cppSetRenderImage ()
at rive::ImageAsset::renderImage ()
at ()
The crash occurs during runtime (not at initialization) when the Rive engine processes an image asset within a .riv file.
Initialization
Rive.init(context, defaultRenderer = RendererType.Rive)
Rive animations are rendered via Compose using AndroidView.
Android 16 is disproportionately affected — it represents a much smaller share of our user base but accounts for most of these crashes. This suggests a potential compatibility issue with Android 16's 16KB page size, memory tagging, or GPU driver changes.
Versions, Device, and Other Information
Device Distribution
The crash predominantly affects Samsung flagship devices (Galaxy S22–S25 series) and Pixel devices running Android 16. Architecture is consistently arm64-v8a.
Environment
- Rive Android version: 11.1.2
- Renderer: RendererType.Rive
- Architecture: arm64-v8a
- Crash mechanism: signalhandler (native signal, not Java exception)
- Level: fatal / unhandled
Possibly Related Issues
- App crashed at librive-android.so on SDK Android 15 and 16kb page size supported device #329 — librive-android.so crash on Android 15/16 with 16KB page size (fixed in Fix bug crash on Android 15 (with 16KB page size support) #331)
- App crash due to missing libraries for
x86,armeabi-v7a,armeabi#341 — App crash due to missing libraries for certain ABIs - Rive crashes when RiveAnimationView leaves the screen #313 — Crash when RiveAnimationView leaves the screen (SIGSEGV during cleanup)
Expected Behavior
Rive animations with image assets should render without native crashes across all supported Android versions.