fluxer app lib tests: intermittent SIGSEGV at process exit after all tests pass #304

Open
opened 2026-11-12 14:06:42 +00:00 by charles · 0 comments
Owner

Seen while running FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci on branch textchat-6-api-chat-endpoints at 31b48f6 (parent b3179a2), Linux (CachyOS).

cargo test -p fluxer --lib printed test result: ok. 53 passed; 0 failed and the process then died with signal: 11, SIGSEGV: invalid memory reference, failing the test step. The next three runs of cargo test -p fluxer --lib and the next full xtask ci passed. The change under test touched only fluxer-api and fluxer-proto, so it looks like a teardown crash in a native dependency of the app crate (e.g. audio/WebRTC threads still running at exit).

Steps to reproduce: run FLUXER_SCREENSHOT_TESTS=1 cargo test -p fluxer --lib repeatedly; about 1 in 4 runs here.

Seen while running `FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci` on branch `textchat-6-api-chat-endpoints` at 31b48f6 (parent b3179a2), Linux (CachyOS). `cargo test -p fluxer --lib` printed `test result: ok. 53 passed; 0 failed` and the process then died with `signal: 11, SIGSEGV: invalid memory reference`, failing the `test` step. The next three runs of `cargo test -p fluxer --lib` and the next full `xtask ci` passed. The change under test touched only `fluxer-api` and `fluxer-proto`, so it looks like a teardown crash in a native dependency of the app crate (e.g. audio/WebRTC threads still running at exit). Steps to reproduce: run `FLUXER_SCREENSHOT_TESTS=1 cargo test -p fluxer --lib` repeatedly; about 1 in 4 runs here.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#304
No description provided.