[Android] updateAndRelease: EGLConsumer is not attached to an OpenGL ES context

[NikitaDudin]

Description

Logcat error appears on the skia canvas draw call on the Android platform.

Error message:

[SurfaceTexture-0-26661-50] updateAndRelease: EGLConsumer is not attached to an OpenGL ES context

Version

0.1.227

Steps to reproduce

Just add skia canvas scene

<Canvas style={{ flex: 1 }}>
  <Fill />
</Canvas>

[wcandillon]

This exception is expected, the log message right after should indicate it.
We understand that this is confusing but for now we don't have a better solution for this.
We may update the rendering logic there but not in the short term.

[NikitaDudin]

Seems like error in this place
https://github.com/AOSPA/android_frameworks_native/blob/a097e4c621cea5231a1c12ca20b5db93ea54bdbd/libs/nativedisplay/surfacetexture/SurfaceTexture.cpp#L107 -> https://github.com/AOSPA/android_frameworks_native/blob/a097e4c621cea5231a1c12ca20b5db93ea54bdbd/libs/nativedisplay/surfacetexture/EGLConsumer.cpp#L118 ->
https://github.com/AOSPA/android_frameworks_native/blob/a097e4c621cea5231a1c12ca20b5db93ea54bdbd/libs/nativedisplay/surfacetexture/EGLConsumer.cpp#L239

Indeed, it looks like an internal log, albeit with an error level

[wcandillon]

this is the file where it happens: https://android.googlesource.com/platform/frameworks/native/+/5c1139f/libs/gui/SurfaceTexture.cpp
The problem is that we have little control over this API and it's based on many private APIs (preventing us to build something that fits our needs). But I may have overlooked something.

[NikitaDudin]

Okay, thank you for clarification! 🙏

[jatin-bhuva]

Any updates on this issue?

[wcandillon]

We haven't identified this as an issue. What would you qualify as an issue?

…

On Wed, May 8, 2024 at 9:02 AM Jatin ***@***.***> wrote: Any updates on this issue? — Reply to this email directly, view it on GitHub or unsubscribe. You are receiving this email because you commented on the thread. Triage notifications on the go with GitHub Mobile for iOS or Android.

[jatin-bhuva]

Okay, So I want clarification on this logcat error message, will it make any impact on the performance-related issues on android devices?
Initially, I had below errors:
dequeueBuffer: BufferQueue has been abandoned
and

 eglSwapBuffers failed: 12301
  egl_window_surface_t::swapBuffers called with NULL buffer
  tid 15054: swapBuffers(781): error 0x300d (EGL_BAD_SURFACE)

So I upgraded the library version and now no issue with that but receiving updateAndRelease: EGLConsumer is not attached to an OpenGL ES context](https://github.com/Shopify/react-native-skia/issues/2054#top)

So is there need to worry about this?

[wcandillon]

no there is no need to worry about this exception. We do have plans to remove it eventually.

…

On Wed 8 May 2024 at 09:24, Jatin ***@***.***> wrote: Okay, So I want clarification on this logcat error message, will it make any impact on the performance-related issues on android devices? Initially, I had below errors: dequeueBuffer: BufferQueue has been abandoned and eglSwapBuffers failed: 12301 egl_window_surface_t::swapBuffers called with NULL buffer tid 15054: swapBuffers(781): error 0x300d (EGL_BAD_SURFACE) So I upgraded the library version and now no issue with that but receiving updateAndRelease: EGLConsumer is not attached to an OpenGL ES context]( #2054 (comment)) So is there need to worry about this? — Reply to this email directly, view it on GitHub <#2054 (comment)> or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACKXVXGUR65E2GKQKFEGDDZBHHLZBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZTKMRZGIYDEMBWGSSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJUGI2TQNBVGMZDLAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDEMBUGA2DCMBYGUYIFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZTKMRZGIYDEMBWGSTXI4TJM5TWK4VGMNZGKYLUMU> . You are receiving this email because you commented on the thread. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .

[rohithnair1996]

@wcandillon Is there any update on this? I’m working on a multiplayer app with many animations, and after a large number of animations run, the app force-closes.

[wcandillon]

@rohithnair1996 does the app closes because of a crash? if yes what kind of crash is it?