Forumics logo Forumics
Issue 01

Back to issue

All Zed known issues

CLAIM C107 Supported 2026-11-12

GitHub issue #53015 in zed-industries/zed, opened 2026-04-02 by m-ar-c, records a report that exporting a 468 MB SQL file at the root of a project caused Zed to use a huge amount of RAM and crash the reporter's GNOME session, reproduced as soon as Zed opened because the Uncommitted Changes tab was restored, and reproducible just by opening that tab, with RAM continuing to grow after closing it, and the problem gone if the file is removed; the report was filed against Zed v0.230.0 on Linux Wayland Debian sid with 15.3 GiB of memory.

Verbatim Excerpts from Cited Records
“I exported a sql file at the root of my project, then zed used huge amount of RAM and made my Gnome session crash.”
— m-ar-c · zed-industries/zed (issue 53015 opening body, Reproduction steps section) · 2026-04-02T17:49:57Z ·GitHub Issue ↗
“The issue was reproduced as soon as I opened zed (because the 'Uncommited Changes' tab was restored).”
— m-ar-c · zed-industries/zed (issue 53015 opening body, Reproduction steps section) · 2026-04-02T17:49:57Z ·GitHub Issue ↗
“I can reproduce by just opening the 'Uncommited Changes' tab. Closing it does nothing, RAM continues to be eaten more and more.”
— m-ar-c · zed-industries/zed (issue 53015 opening body, Reproduction steps section) · 2026-04-02T17:49:57Z ·GitHub Issue ↗
“Problem gone if I remove the file.”
— m-ar-c · zed-industries/zed (issue 53015 opening body, Reproduction steps section) · 2026-04-02T17:49:57Z ·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 11 comments were read. zed-community-bot (2026-04-02) flagged a possible duplicate of #27283; m-ar-c (2026-04-02) disputes it, noting the file itself opens fine. miguelraz (2026-04-02 and 2026-04-21) asked for a shareable reproduction file; m-ar-c (2026-05-06) retested with a generated 469 MiB fake dump and supplied it, and (2026-06-29) reproduced again with a 416 MB file, Zed consuming over 65% of RAM before the session crashed. m-ar-c (2026-10-02) retested on Zed v1.22.0 and confirms it is still relevant. SilicalNZ (2026-11-11) reports the same with a 1.7 GB .sql file, Zed eating 23 GB of memory until the system killed it, reproduced on v1.24.4 and v1.27.0. 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. Falsification probe: If GitHub issue #53015 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.