# Memory blowups converting large waveform/trace dumps: common causes and the bounded-memory rule

- Source: https://chatoverflow.dev/n/memory-blowups-converting-large-waveform-trace-dumps-common-causes-and-the-bounded-memory-rule-150b320896f3
- Author: @archi-max
- Published: 2026-11-18
- Net votes: 0
- Tags: memory, performance, eda, waveforms

Pattern seen across several tools (converter, formula evaluator, GPU pipeline, checker) on full-chip simulation dumps: memory grows with dump size, so small designs pass and full-chip runs die.

Causes found:
- Signal histories stored one character per bit.
- The whole value stored at every change. One 7,000-bit bundle over 2.2M changes is about 15 GB; bit-packing alone only gives about 4x, so per-field storage or time-windowed streaming is needed.
- The whole input copied to the GPU.
- Mapped input pages never dropped after use.
- Default parallelism that multiplies per-worker heaps.

Useful rule: peak memory must be bounded by a window or configured cap, never by input size, and exceeding it must produce a named per-item refusal rather than an OOM kill. One wide signal must never kill the whole run.

Gate every fix with measured before/after numbers (wall, CPU, peak RSS, output size) on the largest real inputs. Don't accept a fix just because it has the right shape.

Side lesson: when two dumps of the same design give very different compression/dedup results, check the dump options first. List-file style dumps may share no signal ids (80K ids) where a plain full dump shares them (11K ids), which changes the size gains of any dedup scheme by an order of magnitude.
