Emulator Issues #14131
openConsistent GUI buffering (Windows x64) rendering Dolphin functionally stalled --> Qt-style/theme related?
0%
Description
Dolphin UI - not game specific
What's the problem? Describe what went wrong.
In v2606a (Windows x64) -- most recently deployed version.
State problem was discovered in:
- New install
- VS dependencies accounted for
- Under Controller:
Dolphin immediately becomes not responsive and heavily stalls for consistent periods of 4.7 seconds. This is most and readily problematic on version 2026a, and is less responsive than the 2023a UI under the same minimal set of interactions (i.e. leaving the UI completely idle.) This problem is persistent across several menu settings and consequently hangs the emulator during gameplay.
Attached is a local Winbdg analysis.txt file. Getting to the log file is as far as my knowledge goes.
What are your PC specifications? (CPU, GPU, Operating System, more)
CPU Model : 12th Gen Intel(R) Core(TM) i7-12700K
Physical Cores : 12
Logical Threads : 20
Max Clock (MHz) : 3600
GPU Model : NVIDIA GeForce RTX 3070
VRAM : 8 GB
GPU Driver : 32.0.16.1074
Stack Trace of the Issue:
00 win32u!NtUserSystemParametersInfo+0x14
01 USER32!RealSystemParametersInfoW+0x123
02 UxTheme!ClassicSystemParametersInfoW+0x38
03 UxTheme!ThemeSystemParametersInfoW+0xbc
04 USER32!SystemParametersInfoW+0x5a
05 Qt6Widgets!QWindowsStylePrivate::pixelMetricFromSystemDp+0xf7
06 Qt6Widgets!QWindowsStyle::pixelMetric+0x32
07 qwindowsvistastyle!qt_plugin_instance+0xf1a4
08 Qt6Widgets!QPushButton::`default constructor closure'+0x17890
09 Qt6Widgets!QScrollBar::sizeHint+0xb0
0a Qt6Widgets!QSystemTrayIcon::messageClicked+0x144a
0b Qt6Widgets!QSystemTrayIcon::messageClicked+0x1052
0c Qt6Widgets!QAbstractScrollArea::event+0x545
0d Qt6Widgets!QApplicationPrivate::notify_helper+0x10e
0e Qt6Widgets!QApplication::notify+0x1877
0f Qt6Core!QCoreApplication::notifyInternal2+0xc5
10 Qt6Widgets!QWidgetPrivate::setStyle_helper+0x1ed
11 Qt6Widgets!QWidgetPrivate::inheritStyle+0x191
12 Qt6Widgets!QWidgetPrivate::setStyle_helper+0x12f
13 Qt6Widgets!QWidgetPrivate::inheritStyle+0x191
14 Qt6Widgets!QWidgetPrivate::setStyle_helper+0x12f
15 Qt6Widgets!QWidgetPrivate::inheritStyle+0x191
16 Qt6Widgets!QWidgetPrivate::setStyle_helper+0x12f
17 Qt6Widgets!QWidgetPrivate::setStyle_helper+0x12f
18 Qt6Widgets!QWidgetPrivate::inheritStyle+0x191
19 Qt6Widgets!QWidgetPrivate::setStyle_helper+0x12f
1a Qt6Widgets!QWidgetPrivate::setStyle_helper+0x12f
1b Qt6Widgets!QWidgetPrivate::inheritStyle+0x191
1c Qt6Widgets!QWidgetPrivate::setStyle_helper+0x12f
1d Qt6Widgets!QWidgetPrivate::inheritStyle+0x191
1e Qt6Widgets!QWidget::setStyleSheet+0x94
1f Qt6Widgets!QApplication::setStyle+0x211
20 Qt6Widgets!QApplication::setStyle+0x21
21 Dolphin+0x2220ac
22 Dolphin+0x11e856
23 Qt6Widgets!QWidget::event+0x85e
24 Qt6Widgets!QApplicationPrivate::notify_helper+0x10e
25 Qt6Widgets!QApplication::notify+0x1877
26 Qt6Core!QCoreApplication::notifyInternal2+0xc5
27 Qt6Widgets!QWidgetRepaintManager::rhi+0x268c
28 Qt6Widgets!QApplicationPrivate::notify_helper+0x10e
29 Qt6Widgets!QApplication::notify+0x1877
2a Qt6Core!QCoreApplication::notifyInternal2+0xc5
2b Qt6Gui!QGuiApplicationPrivate::processThemeChanged+0x23e
2c Qt6Gui!QWindowSystemInterface::sendWindowSystemEvents+0x80
2d Qt6Gui!QWindowSystemInterface::flushWindowSystemEvents+0x183
2e qwindows!qt_plugin_instance+0x5eae
2f qwindows!qt_plugin_instance+0x7635
30 USER32!UserCallWinProcCheckWow+0x356
31 USER32!DispatchClientMessage+0x9c
32 USER32!_fnDWORD+0x33
33 ntdll!KiUserCallbackDispatcherContinue
34 win32u!NtUserDispatchMessage+0x14
35 USER32!DispatchMessageWorker+0x348
36 Qt6Core!QEventDispatcherWin32::processEvents+0x506
37 Qt6Gui!QWindowsGuiEventDispatcher::processEvents+0x19
38 Qt6Core!QEventLoop::exec+0x1c4
39 Qt6Core!QCoreApplication::exec+0x169
3a Dolphin+0x1cfdf1
Main issue seems to be constant, repeated calling of:
- QWidgetPrivate::setStyle_helper
- QWidgetPrivate::inheritStyle
- QWidgetPrivate::setStyle_helper
occurring on the UI thread, causing the whole display to buffer.
It seems there's an issue with the event handler miscalling/overcalling widgets. It is easier to get 2026a to stall than 2023a in the controller/configuration menu via button spam, however, the stalling is agnostic to which menu it's on.
Files
No data to display