Details
-
Bug
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
6.8.3
-
None
Description
Observing this when analyzing our users' crashes in Sentry.
It's never reproduced in our testing environment, so I have no idea about step/preconditions.
Unhandled exception at 0x00000242932DB790 in 6c37ee1b-5697-4be0-ae20-7f6d647bb54a.dmp: 0xC0000005: Access violation executing location 0x00000242932DB790.
Call stack:
00000242932db790() Unknown Qt6Core.dll!doActivate<0>(QObject * sender, int signal_index, void * * argv) Line 4140 C++ Qt6Core.dll!QMetaObject::activate(QObject * sender, const QMetaObject * m, int local_signal_index, void * * argv) Line 4184 C++ > Qt6Quick.dll!QSGRenderThread::syncAndRender() Line 808 C++ Qt6Quick.dll!QSGRenderThread::run() Line 979 C++ Qt6Core.dll!QThreadPrivate::start(void * arg) Line 273 C++ [External Code]
Crashed on trying to call window->afterFrameEnd() in QSGRenderThread::syncAndRender(). Perhaps the window is already destroyed.
Attachments
Issue Links
- relates to
-
QTBUG-132653 Render thread calls into window after window has already been destroyed
-
- Reported
-