{"version":"2.1.314","anchor":"page-text-decoder-now-throws-on-suspected-out-of-memory-deco","canonical_anchor":"page-text-decoder-now-throws-on-suspected-out-of-memory-deco","heading":"Reading a very large page now fails with a clear out-of-memory error","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/page-text-decoder-now-throws-on-suspected-out-of-memory-deco","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Reading a very large page now fails with a clear out-of-memory error\n\nWhen decoding a page's text runs out of memory, Claude Code now stops reading and reports \"out of memory while decoding a page\"\n\n**What**\n\nWhen Claude Code reads a page as a stream, piece by piece, it now watches for a sign that it ran out of memory: a piece of data that decodes to no text at all. When that happens, it stops reading and reports the error \"out of memory while decoding a page\". The code that did this before was broken.\n\n**Why**\n\nFetching or reading a very large page now fails with a clear error instead of quietly returning only part of the text.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}