Document Node 24 crash scope and concurrent-render diagnostic - #11
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README describes broad Node CI coverage but does not identify the intermittent Linux / Node 24.21.0 process crash tracked in #7. Add that limitation and retain a synthetic diagnostic that exercises overlapping PDF and preview workers while V8 collects WebAssembly code.
One bounded run used the published, unchanged
fullbleed@0.1.3package under GDB: 84 completed renders, four peak workers, zero workers left, 64 code-collection starts, and 13 wrapper-free events. Every output matched its serial baseline; all eight baseline PDF/PNG files also matched the published release samples. The original crash remains unresolved.Validation: the checked-in diagnostic is byte-identical to the executed script, the Linux Node binary matches its checksum-verified official archive, four retained PDFs passed an independent reader, and documentation links, shell syntax, JavaScript syntax, and diff whitespace checks passed. The evidence record includes the retained archive's SHA-256. Package runtime, engine dependency, version, and production configuration are unchanged.