-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPUI window resizes are very slow on Linux #15311
Comments
It looks like most of the time here is spent in the blade resize, thoughts on what the issue could be there @kvark? |
No one seems to be able to reproduce this on any Nvidia cards or Intel iGPUs yet. Might be a problem with RADV (the libvulkan_radeon.so in the flamegraph) specifically. |
Got this issue also. Wayland. NVIDIA 960. Driver Version : 550.78 |
I have slightly different issue, mine crashes
|
What is the output of |
|
I also got this issue on Wayland. Resizing takes 5 to 10 seconds. If i try to do something while resizing like clicking on zed it also stops responding. |
@roverflow that is interesting. Here are the things that would be great to try if you have time:
|
wanting to try zed but funny enough the first thing I do opening a window is to try and resize it... I'm on arch linux with KDE plasma, and maybe complicated having three gpus (an amd card, an nvidia card, integrated)
Here's the output from running zed
As a hack (which is the same method I discovered to solve my chromium gpu problems), I can run zed in a bubblewrap environment, exposing it to only one GPU.
the output is
still see that |
@digitalsignalperson that's interesting, and weird. Having multiple physical devices that aren't used by the current context shouldn't affect the resize speed. Perhaps, you are just making it run on a different physical device when bubblewrapping? |
@kvark yes the bwrap example is preventing 2 of the gpu's from being seen by the program, forcing it to use one I pick and preventing any code paths that might get confused by multiple devices I guess. Normally the simple solution is to set To confirm if multiple GPUs is the culprit, others could provide details if they have both an integrated and discrete gpu enabled |
I've got this problem an I'm using only a single GPU (Nvidia 980, RHEL, KDE) I've also tried it on a different machine (Nvidia 1050, Fedora, KDE) to the same effect. |
Unsure if this helps, but I have a slightly unique situation so I'll throw my experience on the pile. I recently (a few days ago) switched out my old NVIDIA RTX 3060 (driver version 555) for an AMD Radeon RX 6750 XT. On the Nvidia card the slow resizes were very noticeable and quite extreme, sometimes taking multiple seconds to resolve and creating artifacts during. However, on the AMD, the resizes are quite a bit faster. Still noticeably slower than other windows, but always resolving in under a second and without the same artifacts. I'm using EndeavourOS with KDE Plasma under wayland. |
Able to reproduce. I'm using Arch Linux, NVIDIA 560.35 drivers KDE Plasma 6.2.0 and a RTX 3070 as the GPU. Had this problem for atleast 1.5-2 months. |
@ssynaptics would you be able to grab a sampling profile trace from this scenario, when running on Zed that has debug symbols? |
I experienced resize lagging on the Hello World example for GPUI on Arch Linux (x86_64) with an NVIDIA RTX 3070 Ti. Flamegraph attached.
|
@MeguminSama thank you! This flamegraph doesn't have Zed code symbols though. |
It appears that when the window size is small the resize is not as laggy as it is when the window size increases. 2025-01-09.20-29-22.mp4 |
Able to reproduce with CachyOS x86_64 with a NVIDIA RTX 3060, resizing is faster at lower resolutions as edfloreshz said. Full-screening is instant.
Video_2025-02-05_22-17-29.mp4 |
Same problem with ubuntu + NVIDIA RTX 500 |
Check for existing issues
Describe the bug / provide steps to reproduce it
When Zed (or seemingly any GPUI based app) is opened and resized on Linux, the actual window resize operation takes multiple seconds, and freezes the entire application while this is occurring.
This issue is substantially worse after I pulled GPUI today.
Environment
Zed: v0.145.1 (Zed)
OS: Linux Wayland arch unknown
Memory: 31 GiB
Architecture: x86_64
If applicable, add mockups / screenshots to help explain present your vision of the feature
As requested in the Zed Discord, attached is a flamegraph of my application (https://github.com/143mailliw/muzak) exhibiting this issue. Most of the time is spent in various calls to the AMD Vulkan driver from
blade_graphics
. It's in a ZIP file to avoid github sanitizing the SVG.flamegraph.zip
If applicable, attach your Zed.log file to this issue.
No response
The text was updated successfully, but these errors were encountered: