Forumics logo Forumics
Issue 01

Back to issue

All Zed known issues

CLAIM C043 Supported 2026-11-07

GitHub issue #58190 in zed-industries/zed, opened 2026-05-31 by martin-c, records a report that on a 64 GB M1 Max Mac Studio running Zed 1.4.4 stable on macOS 15.6.1, a single Zed process grew to 391 GB resident and drove the whole system into terminal memory pressure, that the growth coincided with a continuous main-thread hang lasting at least about 2 hours, and that the reporter argues no single subsystem should be able to consume several times physical RAM and take down the OS.

Verbatim Excerpts from Cited Records
“On a 64 GB M1 Max Mac Studio, a single Zed process grew to **391 GB resident** (≈391 GB of it held in the macOS memory compressor) and drove the entire system into terminal memory pressure: the kernel spent hours shedding background daemons via jetsam, the UI froze, and unrelated applications crashed on failed allocations until I force-rebooted.”
— martin-c · zed-industries/zed (issue 58190 opening body, Summary section) · 2026-05-31T23:33:39Z ·GitHub Issue ↗
“The runaway growth coincided with a **continuous main-thread hang that lasted at least ~2 hours** (Zed's own watchdog logged "hang detected" once per second from 14:18 onward).”
— martin-c · zed-industries/zed (issue 58190 opening body, Summary section) · 2026-05-31T23:33:39Z ·GitHub Issue ↗
“Regardless of trigger, the invariant that's violated is: **a buggy or chatty language server must not be able to make Zed consume multiples of physical RAM and OOM the machine.**”
— martin-c · zed-industries/zed (issue 58190 opening body, Why this is a Zed bug, not just a bad LSP section) · 2026-05-31T23:33:39Z ·GitHub Issue ↗
“Growth rate implied: roughly **15–20 MB/s sustained for ~5–6 hours**.”
— martin-c · zed-industries/zed (issue 58190 opening body, Timeline section) · 2026-05-31T23:33:39Z ·GitHub Issue ↗
Counter-record: Issue closed 2026-11-06 by the reporter martin-c, who wrote he was not able to reproduce it and would reference this issue if a similar crash recurred; the closure records non-reproduction, not a refutation of the original incident. 23 comments surveyed as of 2026-11-06. A maintainer (Anthony-Eid) asked for crash reports and the hang trace on 2026-06-01 and 2026-06-03; the reporter replied the hang-trace files were empty and set up memory monitoring. A second user (olejorgenb) reported similar growth on Linux after upgrading to Zed 1.5.4 on 2026-06-06, and another (code3z) reported Zed growing to 58 GB on 2026-08-01. The reporter updated on 2026-08-04 that with monitoring active he had seen no recurrence since the original incident. Several off-topic comments from troubleduser00-beep on 2026-07-29 contain no usable reproduction. No maintainer fix or resolution appears in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If issue 58190 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.