Bug 460034

Summary: Frame skip during window resizing
Product: [Plasma] kwin Reporter: Puspam Adak <puspitaadak9876>
Component: auroraeAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 5.25.5   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Puspam Adak 2022-10-06 07:06:56 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Kwin constantly skips frames during & after window resizing. Since maximizing windows also results in resizing, frame skip occurs in that case too. I have tested this using glxgears.
There is no frame drop as reported by glxgears, but visibly, the animation gets paused for around 500ms after resizing a window. This skip is also visible on videos playing in VLC. Hence, it seems that kwin is skipping some frames after resizing windows.
Resizing CSD windows doesn't cause this problem.

STEPS TO REPRODUCE
1. Open any application (non-csd)
2. Open glxgears.
3. Resize the window/maximize it.
3. Observe glxgears pause for a few moment.

OBSERVED RESULT
Kwin skips some frames for the whole desktop after resizing any window.

EXPECTED RESULT
Kwin should display every frame without skipping any.

SOFTWARE/OS VERSIONS
Linux: 5.15.70-1-lts
(available in About System)
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION
GPU: Mesa IntelĀ® HD Graphics 2500
Comment 1 Puspam Adak 2022-11-05 14:14:25 UTC
I have found out that frame skip occurs only when using SVG-based aurorae window decorations. If the decoration is a compiled one such as Breeze, no frame skip occur.
I hope it have something to do with Kwin somehow blocking the render thread during resizing SVG graphics.
Comment 2 Nate Graham 2023-01-17 22:12:54 UTC

*** This bug has been marked as a duplicate of bug 446166 ***