Closed paperdave closed 2 weeks ago
today i just hit this again when opening bun today. my workspace is soft-locked. restarting the editor seems to fix it.
part of my issue is #7195 (stuff seems to be more stable when excluding large folders), but this still shouldnt cause hangups in the editor
I noticed a git
process stuck at 100% CPU usage owned by zed
when this happens. As soon as I kill it, the UI becomes responsive again.
It's trying to git blame
a large (41k line) file from https://github.com/NixOS/nixpkgs
git blame --incremental --contents - pkgs/top-level/all-packages.nix
Edit: Disabling inline_blame
works around this issue (after restarting the editor).
Check for existing issues
Describe the bug / provide steps to reproduce it
WebKit/WebKit
from GitHubEnvironment
Zed: v0.133.7 (Zed) OS: macOS 13.6.2 Memory: 64 GiB Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
https://github.com/zed-industries/zed/assets/24465214/840b16ec-f47f-4c69-b0a0-d3d54b0a8219
This is a huge step up from my last "zed is slow" issue, where opening this or Bun just hung the entire editor, not even able to view tree items. It's overall pretty responsive, but some actions can hang a few seconds.
I think sometimes it's possible to start search queries that end up blocking other UI actions, even if you attempt to cancel the search or move your focus away from it.
WebKit also contains a lot of C++, JS, Python, Ruby, and I think even some Rust code. I've noticed in other sessions that performing searches ends up starting these language servers just for the previews.
Since WebKit is a submodule inside of Bun, sometimes the Bun workspace itself gets a little laggy, perhaps due to what is in WebKit.
I think my proper solution is to exclude WebKit and related paths in my config, but I think it is still worth considering that having a very heavy workspace impacts UI actions that should be given higher priority. Opening and closing files should always be instant.
[also, i do want to say that i really love how this editor has been feeling and performing in the 90% case. its amazing, the above is an important outlier]
If applicable, attach your
~/Library/Logs/Zed/Zed.log
file to this issue.I suspect unexpected item after pane was dropped was me spamming Cmd+W and
:wq
queueing up actions.