-
Notifications
You must be signed in to change notification settings - Fork 967
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
Use GL backend run water example weird on Android #2416
Comments
GL
and or VULKAN
backend crashed on Android 8.1GL
and or VULKAN
backend failed on Android 8.1
GL
and or VULKAN
backend failed on Android 8.1
The lack of water is expected on GL in general (not limited to Android), since it relies on read-only depth attachment. The crash is unexpected. What's the call stack? |
That crash only observed on Android 8.1, not observed on another Android 10 device. Set Logcat full output:
Graphics Analyzer captured gl function stack: |
Interesting, so this isn't related to read-only depth.
So it looks like a driver bug, but we'll need more information to know exactly. Like a proper call stack. |
I've tried Android Studio debug mode also cann't capture call stack, only throwed last panic message: E/wgpu_hal::gles::egl: GLES: [Other/Performance] ID 2147483647 : Namespace collision detected, using slow path ARM's Graphics Analyzer tool can perfectly debug vulkan, but debug gl always crashed at third frame on all my android phones. If I find a way to get call stack, I'll feed back here. |
I suppose this was closed due to #4031. Since RODS causes undefined behavior on OpenGL (ES), a random crash is in scope. |
Test devices: Google Nexus 5x(Android 8.1.0), Honor V20(HarmonyOS 2.0, based on Android 10)
Reproduce the issue's demo, which used wgpu master branch
water example only see land and no water, crashed after 10+ seconds:
The text was updated successfully, but these errors were encountered: