# Thread crash in FMOD::SystemI::updateStreams **URL:** \ **Category:** FMOD Engine\ **Tags:** windows, cpp\ **Created:** [May 14, 2026, 11:13pm UTC](https://qa.fmod.com/t/thread-crash-in-fmod-updatestreams/24265 "2026-05-14T23:13:48Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![elesh](https://avatars.discourse-cdn.com/v4/letter/e/3e96dc/32.png) [@elesh](https://qa.fmod.com/u/elesh)\ **Post date:** [May 14, 2026, 11:13pm UTC](https://qa.fmod.com/t/thread-crash-in-fmod-updatestreams/24265/1 "2026-05-14T23:13:48Z")
I’m working with an old windows product experiencing stalls when releasing sounds. I’ve switched to delayed releasing of sound sources until they are either in a ready or error state as suggested in the documentation. However now I am experience streaming thread crashes (FMOD::SystemI::updateStreams). I don’t understand what could happen between the the old and new release times and how to do this safely. I suspect there is some shared resource being used if the same file is loaded again before the release happens. It doesn’t appear that FMOD::Sound pointers are recycled on subsequent loads though. ---
**Author:** ![elesh](https://avatars.discourse-cdn.com/v4/letter/e/3e96dc/32.png) [@elesh](https://qa.fmod.com/u/elesh)\ **Post date:** [May 15, 2026, 12:08am UTC](https://qa.fmod.com/t/thread-crash-in-fmod-updatestreams/24265/2 "2026-05-15T00:08:55Z")
I suspect the use of FMOD\_OPENMEMORY is my problem here as the provided user memory is still getting freed immediately. ---
**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\ **Post date:** [May 18, 2026, 6:00am UTC](https://qa.fmod.com/t/thread-crash-in-fmod-updatestreams/24265/3 "2026-05-18T06:00:11Z")
Did this end up being the issue? If not: - What’s your exact FMOD version? - Can I get you to use [Debug\_Initialize](https://www.fmod.com/docs/2.03/api/core-api-common.html#debug_initialize) to set your logging level to “LEVEL\_LOG”, and provide me with a log where the issue occurs? ---
**Author:** ![elesh](https://avatars.discourse-cdn.com/v4/letter/e/3e96dc/32.png) [@elesh](https://qa.fmod.com/u/elesh)\ **Post date:** [May 18, 2026, 4:18pm UTC](https://qa.fmod.com/t/thread-crash-in-fmod-updatestreams/24265/4 "2026-05-18T16:18:25Z")
Unfortunately it’s going to take quite a refactor to get both the sounds and user memory freed at the same time. The version is 4.44.56. This definitely seems like a smoking gun consider the notes in the documentation. We’re using streaming sounds and it’s pretty clear about the memory sticking around until sounds until release ☹ ---
**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\ **Post date:** [May 19, 2026, 7:51am UTC](https://qa.fmod.com/t/thread-crash-in-fmod-updatestreams/24265/5 "2026-05-19T07:51:31Z")
You may want to try updating to FMOD Ex 4.44.64 and seeing whether that makes any difference, but I agree that based on what you’ve described it sounds like the real solution would be a refactor. Depending on your setup, it may be worth adjusting all streaming sounds to instead be loaded into memory, but I can definitely understand how that might not be possible given memory overhead constraints. FMOD Ex is also no longer officially supported, so I may not be able to offer much help on any technical issues unless you update to a supported version of FMOD Studio (2.02.00 and up). ---
**Author:** ![elesh](https://avatars.discourse-cdn.com/v4/letter/e/3e96dc/32.png) [@elesh](https://qa.fmod.com/u/elesh)\ **Post date:** [May 19, 2026, 4:01pm UTC](https://qa.fmod.com/t/thread-crash-in-fmod-updatestreams/24265/6 "2026-05-19T16:01:32Z")
Thanks. I’ll post again if pairing the user memory and sound release doesn’t work.