Files
zeekayandHanzo Dev 809dc5823a parse: hold an Office read to one budget, and stop it with its context
The 256 MiB cap was per part, so a file of a few KB could name one sheet,
slide or shared string a hundred times, or decode a part into a tree 33
times its size, and reach gigabytes. A read now spends from one budget:
each part's stated size each time it is read, a node per element decoded,
and the text each table writes. Every charge checks the caller's context.
A part claiming a size past int64 was let through as negative; it is
refused. Style levels resolve in one walk, not one per style.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-23 06:30:47 -07:00
..
2026-09-17 06:19:09 -07:00
2026-09-17 06:19:09 -07:00
2026-09-17 06:19:09 -07:00
2026-09-08 12:57:59 -07:00
2026-09-17 06:19:09 -07:00
2026-09-08 12:57:59 -07:00
2026-09-08 12:57:59 -07:00