GitHub issue #15427 in cline/cline, opened 2026-10-29 by peperonid, records a report that the standalone cline-core service (JetBrains plugin) crashes repeatedly with a JavaScript heap out of memory error (exit code 134) after roughly 6-7 minutes of uptime, that heap snapshots show hundreds of retained duplicate copies of the fully serialized globalState JSON, that the on-disk globalState.json is only 2.5 KB so the 11.6 MB in-memory serialization is itself abnormally large, and that the same crash pattern repeated 3 times in 25 minutes; a later investigation note in the issue states the same root cause as issue #15031, the JetBrains host-bridge state stream queuing every snapshot without backpressure and never dropping a superseded one.
Verbatim Excerpts from Cited Records
“The standalone cline-core service (JetBrains plugin) crashes repeatedly with `JavaScript heap out of memory` / SIGABRT (exit code 134) after roughly 6–7 minutes of uptime. The IDE shows:”
·
cline/cline (issue 15427 opening body, Description section)
·
2026-10-29T13:23:37Z
·GitHub Issue ↗
“* The on-disk `~/.cline/data/globalState.json` is only **2.5 KB**, so the 11.6 MB in-memory serialization is itself abnormally large, and 700+ retained copies of it is a leak.”
·
cline/cline (issue 15427 opening body, Heap snapshot analysis section)
·
2026-10-29T13:23:37Z
·GitHub Issue ↗
“The same crash pattern repeated 3 times in 25 minutes (snapshots at 15:37 PID 7512, 15:52 PID 32356, 15:59 PID 11440), each followed by an automatic service restart. Uptime before crash was consistently \~6–7 minutes.”
·
cline/cline (issue 15427 opening body, Heap snapshot analysis section)
·
2026-10-29T13:23:37Z
·GitHub Issue ↗
“Same root cause as cline/cline#15031: the JetBrains host-bridge state stream queues every snapshot without backpressure and never drops a superseded one. This is the fast variant. An 11.6 MB state (the task had \~1,700 messages before compaction) plus a burst of updates fills the 8 GB heap in about 100 s, where cline/cline#15031 takes hours. Plugin 2.0.9 / core 4.1.26 has the same streaming code as 2.0.7 / 4.1.23.”
·
cline/cline (issue 15427 opening body, Investigation (2026-11-02) note)
·
2026-10-29T13:23:37Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 4 comments were read. peperonid (2026-10-29) added a live reproduction with timings and the observation that task context ballooned to 1.6M tokens / 1737 messages, triggering auto-compact, and that tool-list churn is an amplifier, not the cause. mkondratek (2026-11-02, maintainer) thanked the reporter, confirmed the same root cause as #15031, and said the plaintext-API-key-in-heap-snapshot note is getting its own fix; telemetry and the fix are tracked on #15031 (PRs cline/intellij-plugin#1256 and cline/cline#15492). No retraction or correction of the crash report appears in the surveyed thread. The claim documents only the original report and the investigation note, not a verified current state.
Falsification probe: If GitHub issue #15427 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.