Skip to content

Crash: app.rive.RiveInitializationException: Unable to create EGL context #436

Open

Description

@archie94

Description

Crashlog:

Caused by app.rive.RiveInitializationException: Unable to create EGL context
       at app.rive.core.RenderContextGL$Companion.createContext(RenderContext.kt:233)
       at app.rive.core.RenderContextGL$Companion.access$createConfig$attr(RenderContext.kt:110)
       at app.rive.core.RenderContextGL$Companion.access$createContext(RenderContext.kt:110)
       at app.rive.core.RenderContextGL.getContext(RenderContext.kt:105)
       at app.rive.core.RenderContextGL.<init>(RenderContext.kt:105)
       at app.rive.core.CommandQueue.<init>(CommandQueue.kt:107)
       at com.u.a.fu.fuvp.ViewModel.<init>(ViewModel.kt:571)
Caused by java.lang.Throwable: EGL_BAD_ALLOC
       at app.rive.core.RenderContextGL$Companion.createContext(RenderContext.kt:233)
       at app.rive.core.RenderContextGL$Companion.access$createConfig$attr(RenderContext.kt:110)
       at app.rive.core.RenderContextGL$Companion.access$createContext(RenderContext.kt:110)
       at app.rive.core.RenderContextGL.getContext(RenderContext.kt:105)
       at app.rive.core.RenderContextGL.<init>(RenderContext.kt:105)
       at app.rive.core.CommandQueue.<init>(CommandQueue.kt:107)
       at com.u.a.fu.fuvp.ViewModel.<init>(ViewModel.kt:571)

Versions, Device, and Other Information

  • Rive Android Runtime Version: 11.1.1
  • Rive API: CommandQueue() initialisation
  • Device: Pixel 9 Pro
  • App Minimum SDK Level: Android SDK API Level 36
  • App Target SDK Level: Android SDK API Level 35
  • App NDK Level:
  • Frequency: Rare as of now, however app update with the latest Rive sdk went live recently. Will update with more statistics as I have them.

Activity

  1. ErikUggeldahl commented on Feb 11, 2026

    @ErikUggeldahl
    Collaborator

    Hi @archie94. Thanks for the report and for using the new API. Is this a local reproduction or from analytics? Also, do you set up RiveLog for yourself? Would you be able to get the information coming out of it?

  2. archie94 commented on Feb 12, 2026

    @archie94
    Author

    Hey @ErikUggeldahl ,
    This is from firebase crashlytics.

    Also, do you set up RiveLog for yourself? Would you be able to get the information coming out of it?

    Not on release builds. At the moment we won't be able to give you logs from user devices but let me see if something can be done.

    We are getting another crash on the same SDK version.

    Fatal Exception: java.lang.NullPointerException:
           at app.rive.RiveKt$Rive$7$3.invokeSuspend(Rive.kt:340)
           at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:34)
           at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
           at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.android.kt:79)
           at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch(AndroidUiDispatcher.android.kt:41)
           at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.doFrame(AndroidUiDispatcher.android.kt:68)
           at android.view.Choreographer$CallbackRecord.run(Choreographer.java:2327)
           at android.view.Choreographer$CallbackRecord.run(Choreographer.java:2338)
           at android.view.Choreographer.doCallbacks(Choreographer.java:1498)
           at android.view.Choreographer.doFrame(Choreographer.java:1324)
           at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:2248)
           at android.os.Handler.handleCallback(Handler.java:997)
           at android.os.Handler.dispatchMessage(Handler.java:111)
           at android.os.Looper.loopOnce(Looper.java:237)
           at android.os.Looper.loop(Looper.java:325)
           at android.app.ActivityThread.main(ActivityThread.java:10378)
           at java.lang.reflect.Method.invoke(Method.java)
           at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:635)
           at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:961)
            
    

    This too may have the same RCA as the log points to surface being null where it should not. Let me know if you prefer a separate tracker for this. This crash has a higher occurrence rate.

    Image Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingtriage

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions