Bug 494505 - Resizing window is laggy and causes artifacts
Summary: Resizing window is laggy and causes artifacts
Status: RESOLVED UPSTREAM
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 6.2.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-11 05:46 UTC by gudvinr+kde
Modified: 2024-10-11 17:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Resize artifacts (2.50 MB, video/mp4)
2024-10-11 05:46 UTC, gudvinr+kde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gudvinr+kde 2024-10-11 05:46:15 UTC
Created attachment 174668 [details]
Resize artifacts

SUMMARY

When I resize window, I see black bar during the process and resizing feels laggy.
It's not smooth. Every resize step is noticeable.

This does not happen with firefox, dolphin and probably all other apps I regularly use.

STEPS TO REPRODUCE
1. Open systemsettings
2. Resize

OBSERVED RESULT

Resizing is very laggy, choppy visually and generally unpleasant.

EXPECTED RESULT

Smooth resize as with other apps.


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3
Kernel Version: 6.11.2-arch1-1 (64-bit)
Graphics Platform: X11
Graphics Processor: AMD Radeon RX Vega M GL Graphics
Comment 1 gudvinr+kde 2024-10-11 05:53:55 UTC
Some additional context:

I tried to change settings in "kcmshell6 qtquicksettings" and noticed that with Automatic and OpenGL I see these issues very well.
Vulkan doesn't have same black bar but it produces ghost image of old window state if I make it bigger (and still looks laggy).

Software renderer doesn't seem to have neither but I'd like to use CPU for stuff other than rendering. Why have GPU if it isn't used for something it's intended for.
Comment 2 Nate Graham 2024-10-11 17:40:28 UTC
This is unfortunately a Qt bug deep in the core of how QtQuick works. They need to fix it.