Kirill Bulatov
fca4d60ce1
Needs https://github.com/zed-industries/zed/pull/54635 for the profile overrides added into default settings json to work. Part of https://github.com/zed-industries/zed/issues/48968 Another part of the fix related seems to be https://github.com/zed-industries/zed/pull/45669 ? Using the steps from the issue and profiling on macOs had shown that Zed has 2 memory "leaks" in play when a certain file is being rewritten a lot of times. * First, the thread profiler registers a lot of tasks' data and fills its buffer to the limit: <img width="3456" height="2158" alt="image" src="https://github.com/user-attachments/assets/f183312d-4389-4072-8915-d54e60419b08" /> * Second, if the buffer gets open, the undo history fragments start to creep up infinitely: <img width="3456" height="2158" alt="image" src="https://github.com/user-attachments/assets/61a2b66b-81fd-4973-9c3c-c339f886d9b2" /> The PR aims to solve the first issue by disabling the profiling by default, yet leaving the way to turn in on quickly with settings. The memory usage profiling shows that the memory usage is now dynamically affected by the new setting: <img width="2032" height="1136" alt="image" src="https://github.com/user-attachments/assets/8a6c76b9-6fb7-44bc-ac1d-3c34afe7c575" /> While the test directory being thrashed with the script from the issue, * first, Zed starts with the profiling disabled * then gets the profiling enabled which results in the memory growth close to 1 minute mark of the screenshot * last, the profiling gets disabled again, releasing all the memory accumulated Release Notes: - Improved Zed's default memory usage
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.