CNA-VGAP-034: CNA's audio plan carries two undiagnosed test-suite crashes (AUD-15-021, AUD-15-022) that have not been re-run at this snapshot

CNA snapshot 009d40f5  ·  Known Issues › Verification gaps  ·  source links pinned to 009d40f5

✓

Evidence basis: source-verified at the pinned commit; recorded by CNA's own run (not repeated here); tests exist (not executed for this page). Claims on this page were checked by reading the CNA source at commit 009d40f5; unless a sentence says otherwise, nothing here was built or executed. Nothing on this page was executed unless the Evidence section says so.

An intermittent segfault in AudioMixerSpecOverrideTest within the full audio filter and a heap-corruption abort at teardown after CueTest.*:DynamicSoundEffectInstanceTest.* are recorded as open, blocked on gdb/valgrind.

Identifier
CNA-VGAP-034
Category
Verification gap
Subsystem
Testing & evidence
Status
Open
Verified against
CNA 009d40f5 (009d40f5dd085c4e674d3479675fac84b12b3e0a)
Evidence basis
Recorded by CNA: CNA's own recorded run, not repeated here
Tests touching this area
Yes: see Current tests
Affected contract
The audio test suites (CueTest, DynamicSoundEffectInstanceTest, AudioMixerSpecOverrideTest) and the code they exercise

Expected behaviour

A test suite whose runs can abort with heap corruption hides whether the code under test corrupts memory.

Actual behaviour at TARGET

plan_audio.md lists AUD-15-021 (a 20–40 % segfault in AudioMixerSpecOverrideTest after roughly 1,300 preceding tests, not reproduced in isolation, not caught by ASan) and AUD-15-022 (a deterministic glibc heap-corruption abort at global tear-down with --gtest_filter='CueTest.*:DynamicSoundEffectInstanceTest.*', described as “a real, 100%-reproducible-in-isolation bug that must still be fixed”) as open; NEXTaudio.md records both as blocked on missing gdb/valgrind. The records were made on 2026-07-18, at an earlier revision.

Source locations

Evidence

Read at 009d40f5; not executed (running the suites needs a CNA build). Whether the crashes still reproduce at this snapshot, and whether they come from test code or library code, is unknown; hence a verification gap rather than a bug.

Focused reproduction

No focused reproduction is known. Nothing has been invented here; the evidence above is what exists.

Current tests

The full audio suites run in CI; the records state the crash does not appear in the normal whole-repo or audio-scoped runs.

Regression test

Rerun the two recorded commands at this snapshot under valgrind or with core dumps, then fix or close the entries.

Blast radius

Potentially CueTest/DynamicSoundEffectInstance code paths if the corruption is in library code; unknown.

Workaround

No workaround is known.

The same subject is explained at several altitudes. These are the neighbouring pages at each one.

User guide
Audio: overview