Skip to content

vicash v0.1.8 (long-session OOM hotfix)

Choose a tag to compare

View all tags
@caaatto caaatto released this 04 Jun 14:53
· 2 commits to main since this release
v0.1.8
f2813d2

vicash v0.1.8

Update if you keep vicash open for more than ~30 minutes at a time.

What broke

The unfinished MSMF H.264 / MPEG-TS pipeline behind /stream.ts (shipped as wip reference code since v0.1.0) was auto-spawned every time the relay started. It encoded the capture stream at full framerate continuously, even though nobody was ever consuming /stream.ts. The Microsoft Media Foundation software encoder leaked internal sample buffers on that path. After ~30 minutes of normal use the next encode call returned E_OUTOFMEMORY (0x8007000E), the encoder thread did not handle it gracefully, and the OS abort-trapped the whole process as a "fast fail" (0xc0000409).

The v0.1.7 diagnostic release added a panic hook that would have caught a normal Rust panic, but Windows fast-fail aborts skip the Rust panic path entirely - which is why panic.log stayed empty even after the second crash.

Fix

The leaky encoder no longer auto-spawns. The video_stream module stays in the source tree as wip reference, but it does no work at runtime. If you want H.264 + AAC inside vicash, the fMP4 path added in v0.1.5 (F1 -> Relay -> "Audio im Relay aktivieren") via the optional ffmpeg.exe is the supported way.

Update

If you are on v0.1.5 or v0.1.6 or v0.1.7: open F1, Update -> Install and restart now.

Assets 3
Loading