Large snapshot deserialization memory limits in Vitest

Vitest snapshot testing compares serialized output against stored baseline files using toMatchSnapshot. When verifying recovered data after schema changes, large baseline files can increase memory pressure during the test runner's deserialization phase.

The specific memory threshold at which Vitest encounters exhaustion during snapshot deserialization is not specified. It is also unclear whether large snapshots can be partitioned into smaller baseline files while preserving atomic verification logic for a single recovered data structure.

What memory limits apply to Vitest snapshot deserialization? Can large snapshots be split across multiple files without losing snapshot integrity?