Deliberately far above what this repository compiles. These are backstops
against a hostile declaration, not a size policy: a limit set near the
largest real model buys no safety a limit an order of magnitude above it
lacks, and only turns a legitimate larger federation into a load failure.
The largest recorded package is sixty5 at 657,116,508 bytes, whose glTF
document is 448,823,852 bytes and whose largest buffer is 120,707,064 bytes
across 4 resources (artifacts/ifc/sixty5-first-frame).
documentBytes is the exception, and is generous for a different reason:
both readers decode the document to a string before parsing it, so V8's
maximum string length (536,870,888 bytes) is a wall no ceiling here can
move. One GiB sits above it, so this limit never causes a rejection an
engine would not; raising it further would only allocate more before the
parse fails.
Deliberately far above what this repository compiles. These are backstops against a hostile declaration, not a size policy: a limit set near the largest real model buys no safety a limit an order of magnitude above it lacks, and only turns a legitimate larger federation into a load failure. The largest recorded package is sixty5 at 657,116,508 bytes, whose glTF document is 448,823,852 bytes and whose largest buffer is 120,707,064 bytes across 4 resources (artifacts/ifc/sixty5-first-frame).
documentBytesis the exception, and is generous for a different reason: both readers decode the document to a string before parsing it, so V8's maximum string length (536,870,888 bytes) is a wall no ceiling here can move. One GiB sits above it, so this limit never causes a rejection an engine would not; raising it further would only allocate more before the parse fails.