zed
zed copied to clipboard
zed-industries
Zed hangs when an open file receives a large change on disk
Check for existing issues
- [X] Completed
Describe the bug / provide steps to reproduce it
If a file open in Zed is changed on disk (e.g. through a build script) the change normally just appears in the open buffer (if there are no user changes). If the change is large enough though, Zed just hangs for (what feels like) for ever (spinning beach ball) with 100% CPU usage. Zed can open the same file instantly when opening it after the change.
https://user-images.githubusercontent.com/19362696/221850011-59113b29-3361-4a64-8a54-04b814cc7d2e.mov
openssl rand -base64 1000000 > test.txt
Environment
Zed: v0.74.3 (stable) OS: macOS 13.1.0 Memory: 16 GiB Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response
I have the same problem when opening a large SQL file, no longer able to work with Zed since it always opens my last workspace which I opened that file and CPU goes to 100% as well as RAM...
The behaviour has changed. Zed stays responsive, but a background thread takes all the CPU instead. After a long time the buffer is updated (depending on the change size).