Bug 469485

Summary:	[Win11 + Angle] Moving Krita window crossing the screen border causes severe hiccups
Product:	[Applications] krita	Reporter:	Dmitry Kazakov <dimula73>
Component:	OpenGL Canvas	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	minor	CC:	halla
Priority:	NOR
Version:	git master (please specify the git hash!)
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Dmitry Kazakov 2023-05-08 11:46:34 UTC

STEPS TO REPRODUCE
1. Start dragging Krita's windows across the screen
2. Make sure that the windows crosses the screen's border
3. See the hiccups

The problem happens only with Angle backend, everything works fine with OpenGL backend.

See the demo video: https://disk.yandex.ru/i/PpbccO51hM4vag

First I move the windows with openGL backend (everything works fine), then I switch to Angle and the hiccups start appearing.

VTune points into this backtrace, but I'm not sure how relevant it is:

CPU Time
2 of 11: 23.0%  (0.206s of 0.897s)

d3d11.dll ! func@0x180100c4a
libGLESv2.dll ! rx::StateManager11::setRenderTarget + 0x5b - StateManager11.cpp:1738
libGLESv2.dll ! rx::SwapChain11::copyOffscreenToBackbuffer + 0x283 - SwapChain11.cpp:971
libGLESv2.dll ! rx::SwapChain11::swapRect + 0x41 - SwapChain11.cpp:879
libGLESv2.dll ! rx::SurfaceD3D::swapRect + 0x84 - SurfaceD3D.cpp:322
libGLESv2.dll ! rx::SurfaceD3D::swap + 0x39 - SurfaceD3D.cpp:384
libGLESv2.dll ! egl::Surface::swap + 0xbc - Surface.cpp:324
libGLESv2.dll ! egl::SwapBuffers + 0x97 - egl_stubs.cpp:640
libGLESv2.dll ! EGL_SwapBuffers + 0x87 - entry_points_egl_autogen.cpp:438
qwindows.dll ! QWindowsEGLContext::swapBuffers + 0x44 - qwindowseglcontext.cpp:597
Qt5Gui.dll ! QOpenGLContext::swapBuffers + 0xf3 - qopenglcontext.cpp:1121
Qt5Gui.dll ! QPlatformBackingStore::composeAndFlush + 0x1232 - qplatformbackingstore.cpp:494
qwindows.dll ! QWindowsBackingStore::composeAndFlush + 0x1a3 - qwindowsbackingstore.cpp:236
Qt5Widgets.dll ! QWidgetRepaintManager::flush + 0x424 - qwidgetrepaintmanager.cpp:1189
Qt5Widgets.dll ! QWidgetRepaintManager::sync + 0x2f6 - qwidgetrepaintmanager.cpp:738
Qt5Widgets.dll ! QWidgetWindow::handleExposeEvent + 0x144 - qwidgetwindow.cpp:1031
Qt5Widgets.dll ! QWidgetWindow::event + 0x385 - qwidgetwindow.cpp:347
Qt5Widgets.dll ! QApplicationPrivate::notify_helper + 0x102 - qapplication.cpp:3637
Qt5Widgets.dll ! QApplication::notify + 0x1e2 - qapplication.cpp
libkritaui.dll ! KisApplication::notify + 0xa7 - KisApplication.cpp
Qt5Core.dll ! QCoreApplication::notifyInternal2 + 0x91 - qcoreapplication.cpp:1064
Qt5Gui.dll ! QGuiApplicationPrivate::processExposeEvent + 0x136 - qguiapplication.cpp:3262
Qt5Gui.dll ! QWindowSystemInterface::sendWindowSystemEvents + 0xd9 - qwindowsysteminterface.cpp:1179
Qt5Core.dll ! qt_internal_proc + 0x257 - qeventdispatcher_win.cpp
USER32.dll ! func@0x1800161a0 + 0x134
qwindows.dll ! qWindowsWndProc + 0x5dd - qwindowscontext.cpp:1714
USER32.dll ! func@0x1800161a0 + 0x134
qwindows.dll ! qWindowsWndProc + 0x5dd - qwindowscontext.cpp:1714
USER32.dll ! DispatchMessageW + 0x200
Qt5Core.dll ! QEventDispatcherWin32::processEvents + 0x667 - qeventdispatcher_win.cpp:595
qwindows.dll ! QWindowsGuiEventDispatcher::processEvents + 0x14 - qwindowsguieventdispatcher.cpp:73
Qt5Core.dll ! QEventLoop::processEvents + 0x1e - qeventloop.cpp:139
Qt5Core.dll ! QEventLoop::exec + 0x1c0 - qeventloop.cpp:231
Qt5Core.dll ! QCoreApplication::exec + 0x6c - qcoreapplication.cpp:1375
krita.dll ! krita_main + 0x4138 - main.cc:717
krita.exe ! _tmainCRTStartup + 0x275 - crtexe.c:329
krita.exe ! WinMainCRTStartup + 0x15 - crtexe.c:176
KERNEL32.DLL ! BaseThreadInitThunk + 0x1c
ntdll.dll ! RtlUserThreadStart + 0x27

Comment 1 Dmitry Kazakov 2023-05-08 12:04:11 UTC

After rechecking with VTune it can confirm that the backtrace is correct and it is the only difference between the cases when Krita is hovered over the screen area and screen's borders.

Comment 2 Halla Rempt 2023-06-21 11:32:23 UTC

Is this something we should or could fix?

Comment 3 Bug Janitor Service 2023-07-06 03:45:13 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Bug Janitor Service 2023-07-21 03:45:08 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!