Block a user
arm64 + ASan: clang miscompiles preserve_none continuation chains (2,727 CI test failures)
arm64 + ASan: clang miscompiles preserve_none continuation chains (2,727 CI test failures)
Same root cause as weaseljson#78: aarch64 + clang + ASan + preserve_none corrupts the caller's frame. Tracked upstream as llvm/llvm-project#70577 (AArch64 ghccc/preserve_none call clobbers…
SHOW_MEMORY builds abort on valid input as soon as a second ConflictSet is alive (per-instance totalBytes compared with process-wide mallocBytes)
This mostly doesn't matter, but I guess we can put a comment somewhere saying that SHOW_MEMORY assumes one conflict set at a time
WeaselJson_OVERFLOW depends on chunk framing: partially-parsed literals and \u escapes push tokens onto the nesting stack, so the same document is accepted whole but OVERFLOWs when streamed
parser3: keep the stackSize needed by a document independent of chunking (reserve transient token slots)
parser3: keep the stackSize needed by a document independent of chunking (reserve transient token slots)
How we achieve this is an implementation detail and doesn't belong in the public header
WeaselJson_OVERFLOW depends on chunk framing: partially-parsed literals and \u escapes push tokens onto the nesting stack, so the same document is accepted whole but OVERFLOWs when streamed
Do fix 2 described above but reserve extra for transient tokens in addition to the supplied stackSize. Find an upper bound on the max number of transient tokens and document it. Augment our fuzz…
test_fixup_256 passes on the buggy fixupMaxVersion Node256 code: no test in the repo catches 4ef10b1's false-Commit bug
Replace test_fixup_256 with a regression test for the Node256 fixupMaxVersion false-Commit bug