Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.8.3
-
NDK 26.2.11394342
-
Android
-
2025wk18s1QtforAndroid, 2025wk20s1QtforAndroid
Description
After releasing an update of our app where we upgraded from Qt 6.8.1 to 6.8.3, we’re seeing frequent crashes like this:
SIGSEGV: Segfault #00 pc 0x0000000000070678 /vendor/lib/egl/libGLESv2_mtk.so #01 pc 0x000000000008a687 /vendor/lib/egl/libGLESv2_mtk.so #02 pc 0x000000000008b9d9 /vendor/lib/egl/libGLESv2_mtk.so #03 pc 0x000000000008b225 /vendor/lib/egl/libGLESv2_mtk.so #04 pc 0x000000000008aad3 /vendor/lib/egl/libGLESv2_mtk.so (glDrawElements+70) #05 pc 0x000000000039c989 /data/app/<redacted>/lib/arm/libQt6Gui_armeabi-v7a.so (BuildId: b2232efa3964a449e8fa440c630c49460da106de) #06 pc 0x000000000039def1 /data/app/<redacted>/lib/arm/libQt6Gui_armeabi-v7a.so (BuildId: b2232efa3964a449e8fa440c630c49460da106de) #07 pc 0x00000000002ede3d /data/app/<redacted>/lib/arm/libQt6Gui_armeabi-v7a.so (QRhi::endFrame(QRhiSwapChain*, QFlags<QRhi::EndFrameFlag>)+40) (BuildId: b2232efa3964a449e8fa440c630c49460da106de) #08 pc 0x00000000003bd15d /data/app/<redacted>/lib/arm/libQt6Quick_armeabi-v7a.so (BuildId: ea85ba027241314652934b700d1b7940b1f361c0) #09 pc 0x00000000003bdbf7 /data/app/<redacted>/lib/arm/libQt6Quick_armeabi-v7a.so (BuildId: ea85ba027241314652934b700d1b7940b1f361c0) #10 pc 0x0000000000310ec5 /data/app/<redacted>/lib/arm/libQt6Core_armeabi-v7a.so (BuildId: 9630d22248ed5fa9af6f234bb9e88cb292c1ba84) #11 pc 0x00000000000a90a5 /apex/com.android.runtime/lib/bionic/libc.so (__pthread_start(void*)+40) #12 pc 0x00000000000620a1 /apex/com.android.runtime/lib/bionic/libc.so (__start_thread+30)
This happens:
- With different OpenGL libraries: libGLESv2_mtk.so, libGLESv2_adreno.so, libGLESv2_powervr.so
- On arm64-v8a, armeabi-v7a, and x64, but more commonly on 32-bit armeabi-v7a and generally older devices.
- On various Android devices (see the attached non-exhaustive list).
- On all our supported OS versions, but more frequently on older releases (see attached list).
Unfortunately we have so far been unable to reproduce the issue on any of our test devices. In previous versions of our app this crash happened very infrequently, but now it is affecting a significant percentage of sessions, so something must have changed.
Any ideas as to how to debug this further or what this could be caused by would be appreciated.
I saw that QTBUG-132780 touched the OpenGL code in Qt 6.8.3. Could that be related?
