-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Crah on some android device #54
Comments
Hi, It is indeed an OpenGL issue. I am not familiar with OpenGL, so I won't be able to help a lot. I guess the fact that you don't use a real Android phone might be a problem (missing features?).
These are inside Android framework. 0x3003 is EGL_BAD_ALLOC. From what I read, I could happen if a lot of GLContext have been opened and not closed. |
It's a real android device . I just ran the demo and nothing changed. It's seems something ran wrong with OpenGL or SurfaceTexture |
When did this happen? When calling |
When call
here is the crash log |
Not sure if it is related but the resolution changed (15x12) just after the connection success event. I don't see a reason why. But it is internal to Android and not to this library. I tested your code with my Pixel 4a and it worked as expected. So, It seems to be a device related issue. If you are interesting of having a closer look to the OpenGL/SurfaceTexture part, you can have a look here and here. The code really needs some love but it works till now 🤷 |
Thanks a lot. |
Version
v1.2.0
Which operating systems have you used?
Environment that reproduces the issue
not on a normal android phone.
Is it reproducible in the example application?
Yes
RTMP Server
selfhost rtmp server[worked]
Reproduction steps
I'm try to run the demo on this device but crash.
It's looks like something wrong whit openGL settings
Expected result
streaming succesfully
Actual result
crash immediately
Additional context
Flutter (Channel stable, 3.19.3, on macOS 14.1.1 23B81 darwin-arm64, locale en-CN)
Android SDK version 32.0.0
device android version: android 11
Relevant logs output
The text was updated successfully, but these errors were encountered: