GitHub issue #59159 in zed-industries/zed, opened 2026-06-11 by EV4g, records a report that continuously adding non git-ignored files to a git-synced project, in the reporter's case 200 33 MB .fits files, made Zed start trying to look through the files and use an additional 2 GB of RAM per second, filling up 64 GB of RAM and 64 GB of swap before crashing; memory increased even when the Git window was not open, and after the reporter edited the .gitignore file in a different program Zed stopped requesting 2 GB/s and memory usage went back to normal; the report was filed against Zed 1.6.3 on Pop-OS Cosmic with 64 GB of memory and an AMD HX370 CPU.
Verbatim Excerpts from Cited Records
“After a bit (in my case 200x 33MB .fits files) Zed editor starts trying to look through the files, which results in the editor trying to use an additional 2GB of ram per second, in my case filling up the 64GB ram and 64GB swap before crashing.”
·
zed-industries/zed (issue 59159 opening body, Reproduction steps section)
·
2026-06-11T21:53:34Z
·GitHub Issue ↗
“Note that after manually editting the .gitignore file in a different program, zed stopped requesting 2GB / s, and memory usage went back to normal.”
·
zed-industries/zed (issue 59159 opening body, after the log attachment)
·
2026-06-11T21:53:34Z
·GitHub Issue ↗
“Memory increased even when the Git window was not open.”
·
zed-industries/zed (issue 59159 opening body, after the log attachment)
·
2026-06-11T21:53:34Z
·GitHub Issue ↗
“Continuously add non git-ignored files to the repository”
·
zed-industries/zed (issue 59159 opening body, Reproduction steps section)
·
2026-06-11T21:53:34Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 8 comments were read. zed-community-bot (2026-06-11) flagged a possible relation to #27283, a large-file memory issue; EV4g (2026-06-11) clarified this report is about many small 5-35 MB files totalling 3-6 GB, explicitly when using Git, using memory well above the 128 GB of RAM plus swap available, even when the Git diff is not in focus and the files are not browsed through. Maintainer yeskunall (2026-06-12) asked for a crash reproduction with the performance profiler enabled, noting no crash traces appeared in the supplied log; EV4g (2026-06-12) replied Zed quit to the background on its own, had crashed once, and the last time the whole OS became non-responsive so the system had to be force powered down. firezdev (2026-06-21) reported the same, with a syslog OOM kill of the zed-editor process and a roughly 7-minute freeze. mjkang-estrella (2026-07-30) could not reproduce the runaway memory growth on current stable Zed 1.13.1 on macOS with the same file count and size, 200 33 MiB .fits files, with RSS staying around 237-238 MiB, suggesting a Linux-specific path, a data-content-dependent path, or a fix or regression difference between Zed 1.6.3 and 1.13.1, and called for a current-stable Linux retest with the reporter's real FITS files. github-actions[bot] (2026-10-30) asked for a retest on the latest stable. No maintainer fix and no retraction of the report appear in the surveyed thread. The claim documents only the original report, not a verified current state. This report is distinct from published C107 (zed #53015, a single 468 MB SQL file in the Uncommitted Changes tab) and C043 (zed #58190, a single process growing to 391 GB with a 2-hour main-thread hang and no identified trigger): here the trigger is the continuous addition of many new untracked binary files while Zed watches a git repository, with growth of 2 GB per second even with the Git window closed, stopped by editing .gitignore.
Falsification probe: If GitHub issue #59159 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.