Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Qt 6.9.3 and 6.10.0 black screen and crash

Qt 6.9.3 and 6.10.0 black screen and crash

Scheduled Pinned Locked Moved Solved Mobile and Embedded
2 Posts 1 Posters 495 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    Aldebaran
    wrote on last edited by Aldebaran
    #1

    Hi !

    I'm trying to port an app from 6.9.2 to 6.9.3 or 6.10.0.
    The app work as expected under 6.9.2, but under 6.9.3 the app launch but quickly after first frames the screen turn black (the controls i press blindly still works).
    And under 6.10.0, the app crash after the first few frames.

    There is the debug log of my app under 6.9.3 :

    D/default : 2025-10-23 10:40:59,440 : debug : removeOlds 1761208859 1761208838 20 true "000000"
W/Qt A11Y : AccessibilityNodeInfo with empty contentDescription: -1
W/Qt A11Y : AccessibilityEvent with empty description
W/default : 2025-10-23 10:40:59,937 : warning : QRhiGles2: Failed to make context current. Expect bad things to happen.
W/default : 2025-10-23 10:40:59,937 : warning : Failed to start frame
D/default : 2025-10-23 10:41:07,082 : debug : Updating position acquisition

    Note the QRhiGles2: Failed to make context current.

    There is the part of debug log of my app under 6.10.0 around the crash :

    10-23 09:54:39.548  2136  5564 E ClipboardService: Denying clipboard access to mygloriousqtapp, application is not in focus nor is it a system service for user 0
10-23 09:54:39.879  2136  2764 D CompatibilityChangeReporter: Compat change id reported: 161145287; UID 10512; state: ENABLED
10-23 09:54:39.908  3055  3086 V ShellRecents: [105392812] RecentsController.finishInner: toHome=true userLeave=false willFinishToHome=true state=0
10-23 09:54:39.908  3055  3086 V ShellRecents:   normal finish
10-23 09:54:39.908  3055  3086 V ShellRecents: [105392812] RecentsController.cleanup
10-23 09:54:39.908  3055  3086 V WindowManagerShell: Transition animation finished (aborted=false), notifying core (#9851)android.os.BinderProxy@6c2c375@2
10-23 09:54:39.909  2136  2334 V WindowManager: Finish Transition #9851: created at 10-23 09:54:37.972 collect-started=0.177ms started=0.212ms ready=2.548ms sent=35.657ms finished=1936.638ms
10-23 09:54:39.913  3055  3086 V WindowManagerShell: Track 2 became idle
10-23 09:54:39.913  3055  3086 V WindowManagerShell: All active transition animations finished
10-23 09:54:39.922  2136  2338 I ActivityManager: Killing 21845:com.google.process.gapps/u0a167 (adj 985): empty #17
10-23 09:54:39.922  2136  2338 W ProcessStats: Tracking association SourceState{25a1943 com.google.android.gms.persistent/10167 Fgs #1777405} whose proc state 3 is better than process ProcessState{a0e5eb5 com.google.android.gms/10167 pkg=com.google.android.gms} proc state 8 (1034 skipped)
10-23 09:54:39.927  2136  4758 W PackageConfigPersister: App-specific configuration not found for packageName: com.google.android.apps.nexuslauncher and userId: 0
10-23 09:54:39.930  2136  2764 W PackageConfigPersister: App-specific configuration not found for packageName: com.google.android.apps.nexuslauncher and userId: 0
10-23 09:54:40.184 23517 23578 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 23578 (QtThread), pid 23517 (ancite.xxx)
10-23 09:54:40.558  2136  2338 I ActivityManager: Killing 5188:com.instagram.android/u0a76 (adj 900): remove task
10-23 09:54:40.769  2136  5128 D AutofillSession: handling death of Token{353d7b6 ActivityRecord{3986078 u0 com.instagram.android/.activity.MainTabActivity t12800 f}}} when saving=false
10-23 09:54:40.772  2136  4844 I WindowManager: WIN DEATH: Window{1c3fddc u0 KHCD.ALo}
10-23 09:54:40.774  2136  2336 D DisplayManagerService: Drop pending events for gone uid 10076
10-23 09:54:40.776  2136  5146 I WindowManager: WIN DEATH: Window{ab485be u0 com.instagram.android/com.instagram.android.activity.MainTabActivity}
10-23 09:54:40.782  2136  5158 W WindowManager: Cannot find window which accessibility connection is added to
10-23 09:54:40.786  2136  2338 W ActivityManager: setHasOverlayUi called on unknown pid: 5188
10-23 09:54:40.787  2136  2354 W UsageStatsService: Unexpected activity event reported! (com.instagram.android/com.instagram.mainactivity.InstagramMainActivity event : 23 instanceId : 55826358)
10-23 09:54:40.848 23581 23581 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-23 09:54:40.848 23581 23581 F DEBUG   : Build fingerprint: 'google/redfin/redfin:14/UP1A.231105.001.B2/11260668:user/release-keys'
10-23 09:54:40.848 23581 23581 F DEBUG   : Revision: 'MP1.0'
10-23 09:54:40.848 23581 23581 F DEBUG   : ABI: 'arm64'
10-23 09:54:40.848 23581 23581 F DEBUG   : Timestamp: 2025-10-23 09:54:40.297661100+0200
10-23 09:54:40.848 23581 23581 F DEBUG   : Process uptime: 4s
10-23 09:54:40.848 23581 23581 F DEBUG   : Cmdline: mygloriousqtapp
10-23 09:54:40.848 23581 23581 F DEBUG   : pid: 23517, tid: 23578, name: QtThread  >>> mygloriousqtapp <<<
10-23 09:54:40.848 23581 23581 F DEBUG   : uid: 10512
10-23 09:54:40.848 23581 23581 F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
10-23 09:54:40.848 23581 23581 F DEBUG   : Abort message: '2025-10-23 09:54:40,184 : fatal : Failed to acquire deadlock protector for QAndroidPlatformOpenGLWindow::eglSurface().'
10-23 09:54:40.848 23581 23581 F DEBUG   :     x0  0000000000000000  x1  0000000000005c1a  x2  0000000000000006  x3  00000071e21632e0
10-23 09:54:40.848 23581 23581 F DEBUG   :     x4  1f6b607360651f39  x5  1f6b607360651f39  x6  1f6b607360651f39  x7  7f7f7f7f7f7f7f7f
10-23 09:54:40.848 23581 23581 F DEBUG   :     x8  00000000000000f0  x9  00000075536f3090  x10 0000000000000001  x11 0000007553739058
10-23 09:54:40.848 23581 23581 F DEBUG   :     x12 000000000000ea57  x13 0000000000000078  x14 00000071e2161bf0  x15 000000000000000b
10-23 09:54:40.848 23581 23581 F DEBUG   :     x16 000000755379dd08  x17 000000755377ae90  x18 00000071e1d4c000  x19 0000000000005bdd
10-23 09:54:40.848 23581 23581 F DEBUG   :     x20 0000000000005c1a  x21 00000000ffffffff  x22 00000071e2164000  x23 b4000073a07c11f0
10-23 09:54:40.848 23581 23581 F DEBUG   :     x24 00000071e21636c0  x25 0000000000000000  x26 000000720e093b55  x27 00000071e2164000
10-23 09:54:40.848 23581 23581 F DEBUG   :     x28 00000071e21639c4  x29 00000071e2163360
10-23 09:54:40.848 23581 23581 F DEBUG   :     lr  000000755372a9b8  sp  00000071e21632c0  pc  000000755372a9e4  pst 0000000000000000
10-23 09:54:40.848 23581 23581 F DEBUG   : 16 total frames
10-23 09:54:40.848 23581 23581 F DEBUG   : backtrace:
10-23 09:54:40.848 23581 23581 F DEBUG   :       #00 pc 00000000000599e4  /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: c74277f481a383c87215b672f6465e24)
10-23 09:54:40.848 23581 23581 F DEBUG   :       #01 pc 0000000000308794  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libQt6Core_arm64-v8a.so (BuildId: fbc9ec74d483aaab55ceb7aff25643c6cb48652e)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #02 pc 000000000031f340  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libQt6Core_arm64-v8a.so (BuildId: fbc9ec74d483aaab55ceb7aff25643c6cb48652e)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #03 pc 000000000031fbdc  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libQt6Core_arm64-v8a.so (QMessageLogger::fatal(char const*, ...) const+152) (BuildId: fbc9ec74d483aaab55ceb7aff25643c6cb48652e)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #04 pc 00000000000834c0  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libplugins_platforms_qtforandroid_arm64-v8a.so (BuildId: 1836541d0affcf46b92505cf437d9a29e4419037)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #05 pc 0000000000082f90  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libplugins_platforms_qtforandroid_arm64-v8a.so (BuildId: 1836541d0affcf46b92505cf437d9a29e4419037)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #06 pc 0000000000580720  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libQt6Gui_arm64-v8a.so (QOpenGLContext::makeCurrent(QSurface*)+144) (BuildId: a63cab88e6990271240cb49c76134b23a2db5a9c)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #07 pc 000000000058cf60  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libQt6Gui_arm64-v8a.so (BuildId: a63cab88e6990271240cb49c76134b23a2db5a9c)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #08 pc 000000000058d1ec  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libQt6Gui_arm64-v8a.so (BuildId: a63cab88e6990271240cb49c76134b23a2db5a9c)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #09 pc 000000000049e7b4  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libQt6Gui_arm64-v8a.so (QRhi::create(QRhi::Implementation, QRhiInitParams*, QFlags<QRhi::Flag>, QRhiNativeHandles*, QRhiAdapter*)+152) (BuildId: a63cab88e6990271240cb49c76134b23a2db5a9c)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #10 pc 00000000004ef6b8  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libQt6Quick_arm64-v8a.so (QSGRhiSupport::createRhi(QQuickWindow*, QSurface*, bool)+1036) (BuildId: e226a803f0ff9019687f59357e9fc3572fb2c572)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #11 pc 00000000005f0520  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libQt6Quick_arm64-v8a.so (BuildId: e226a803f0ff9019687f59357e9fc3572fb2c572)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #12 pc 00000000005f0730  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libQt6Quick_arm64-v8a.so (BuildId: e226a803f0ff9019687f59357e9fc3572fb2c572)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #13 pc 0000000000492b4c  /data/app/~~XcgQH4ZkW48eWoVRKVBSBw==/mygloriousqtapp-3oKZEZnWJjnhxkFfBWU6TA==/lib/arm64/libQt6Core_arm64-v8a.so (BuildId: fbc9ec74d483aaab55ceb7aff25643c6cb48652e)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #14 pc 00000000000be6a8  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+208) (BuildId: c74277f481a383c87215b672f6465e24)
10-23 09:54:40.849 23581 23581 F DEBUG   :       #15 pc 000000000005b21c  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: c74277f481a383c87215b672f6465e24)
10-23 09:54:40.902  2136 23584 E ActivityManager: App crashed on incremental package mygloriousqtapp which is 100% loaded.
10-23 09:54:40.906  2136 23585 I DropBoxManagerService: add tag=data_app_native_crash isTagEnabled=true flags=0x2
10-23 09:54:40.906  2136  2796 W NativeTombstoneManager: failed to open /data/tombstones/tombstone_01.pb

    The two behaviors seems releated to the Gles2 context, but i'm not able to dig in it more.
    I have tested a blank app to see what happen, and the app work in all version. So my app must do something that have well worked in past versions, but not anymore.
    It is not clear if it a bug on my side or on Qt side.

    So, is anybody facing the same problem ?
    Thanks in advance.

    1 Reply Last reply
    0
    • A Offline
      A Offline
      Aldebaran
      wrote on last edited by
      #2

      Ok, for anyone that could face this issue;
      QRhiGles2: Failed to make context current. Expect bad things to happen.
      This was usefull, because i have searched around the creation of the Gl context; my main.qml was an ApplicationWindow, and contained a Loader that instantiate an other ApplicationWindow;
      So i imagine those two windows was trying to interact with the same context or something like that.

      I have try to remove this double ApplicationWindow shenanigan, and it works like a charm.
      Don't ask why that was like that, this information is lost in space and time, in a place named "Legacy Zone".

      1 Reply Last reply
      0
      • SGaistS SGaist has marked this topic as solved on

      • Login
      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved