| Summary: | Toggle overview hangs display for a few seconds | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | statauskersa33 |
| Component: | effects-overview | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.4.4 | ||
| Target Milestone: | --- | ||
| Platform: | NixOS | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Video showing 2 monitors a few applications started and how the display hangs when pressing toggle overiew | ||
|
Description
statauskersa33
2025-08-19 12:57:17 UTC
Created attachment 184252 [details]
Video showing 2 monitors a few applications started and how the display hangs when pressing toggle overiew
Sorry, I don't see how to edit the previous message, but I am using Wayland not X11 Your hardware is powerful; this definitely shouldn't be happening. For what it's worth, I have similar hardware (7940U, everything else the same) and toggling overview with animations disabled is 100% instant for me. Is it any better with animations turned on? Does it work as expected in a new clean user account on the same computer? > Is it any better with animations turned on? Well... Depends. Setup: - Still running the same session as when the attached clip has been recorded (laptop has been running 11hours) - Laptop display out (I have disconnected the external display) - power plugged in, everything is set to max performance (same as before) - 2 "browsers" streaming videos at 1080p - Animations set to instant. Toggling overview is not great, about 150-200ms but when trying after a few minutes it can be about 500ms, not pleasant. CPU usage only spikes on a single core to ~45%, also checked the nvme performance it is not being a bottleneck. Testing with Animations speed set 8th step (from the left): - About 800-900ms of frozen screen when it unfreezes i instantly see the overview view. >Does it work as expected in a new clean user account on the same computer? Do you mean a new user or a clean install? A new user account. A clean installation would be a bit of an invasive thing to ask you to do! Though if you can (maybe with a live session via a USB flash drive) that would be useful information to know as well. Basically, anything to narrow down what might specifically might be causing this, especially because I can't reproduce it with almost identical CPU and GPU hardware, which points away from the idea of it being a GPU driver issue or a general code issue with Overview. One thing I haven't mentioned is that it doesn't happen from startup, it happens after running for some time. Same device: After reboot, running for 58mins couldn't replicate (100-150ms toggle overview). Same device, new user after maybe 15 minutes couldn't replicate (100-150ms toggle overview, tried dual monitor also). Thinkpad x270: liveboot couldn't replicate the issue in a few minutes. (100-200ms toggle overview) Huawei D15: liveboot couldn't replicate the issue in a few minutes.(100-200ms toggle overview) I don't know how to replicate the issue, but I had it happen quite a few times - just that today I ran out of patience lol. I will keep an eye out and update when I catch it. One last thing that maybe is related that I noticed that when changing workspace, even if the app on for example is on workspace 1 and is placed on the left half, swapping workspace made the application window spawn in a location as if the app was just started and not on the left side. ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! Cannot be at my setup for a month, cannot attempt to reproduce the issue/havent encountered it again. Also swapped from nix to arch |