GitHub issue #15031 in cline/cline, opened 2026-10-12 by mibangjie38-bit, records a report that cline-core running inside Android Studio grows until it hits the 8 GB heap limit and dies, killing the session mid-task, that the heap is 98 percent strings and it is one payload copied 1111 times, that a single suspended generator frame holds all 1111 payloads, and that the message translator cannot map session_snapshot to anything and logs and drops it while the producer keeps buffering.
Verbatim Excerpts from Cited Records
“`cline-core` running inside Android Studio grows until it hits the 8 GB heap limit and dies, killing the”
·
cline/cline (issue 15031 opening body, What happened section)
·
2026-10-12T14:44:51Z
·GitHub Issue ↗
“The heap is 98% strings, and it is one payload copied 1111 times.”
·
cline/cline (issue 15031 opening body, What happened section)
·
2026-10-12T14:44:51Z
·GitHub Issue ↗
“**3. Retention chain - a single suspended generator frame holds all 1111 payloads.**”
·
cline/cline (issue 15031 opening body, retention chain section)
·
2026-10-12T14:44:51Z
·GitHub Issue ↗
“The message translator cannot map `session_snapshot` to anything (it logs and drops it)”
·
cline/cline (issue 15031 opening body, producer buffering section)
·
2026-10-12T14:44:51Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 4 comments were read. mibangjie38-bit (2026-10-12) posted two corrections to the report, including that the Build number in Diagnostics was copied from a stale idea.log. mkondratek (2026-10-13, maintainer) thanked the reporter and confirmed the mechanism on the Cline side, noting state updates on the JetBrains path are involved. The same root cause is also named in the investigation note on #15427, which calls this the slower variant of the same leak. No retraction of the crash report appears in the surveyed thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #15031 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.