5 people reported
All time, since Aug 20.
Snapshots serialize entire DOM graph
“Bun recursively walks and serializes the entire JSDOM internal object graph (including Symbol(impl)).”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/bun/issues/4397/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Snapshots and diffs serialize entire DOM object graph. toMatchSnapshot and diff matchers like toEqual walk JSDOM or happy-dom internals, producing multi-megabyte output and memory spikes.
Is this your bug?
File my report- Where
- bun:test expect
- Versions
- 1.3.14 to 1.4.2
- Platforms
- Linux, macOS, Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Failing matcher passes silently3 people
- Test memory grows per file3 people
Original reports5, newest first
expectdiff matchers ignoreutil.inspect.customand serialise the whole object graph on failure#44880- Failing toEqual on a happy-dom element builds a multi-MB diff and can exhaust memory#44707
- bun:test toMatchSnapshot() creates multi-megabyte files when snapshotting JSDOM nodes#44045
- four real bugs found migrating a large test suite (snapshot OOM, plugin override, watch boundary, rejects hang)#40077
- bun:test recursively snapshots JSDOM internals, causing massive memory usage#39768