# Radom Crash in Fmod

**URL:** <https://qa.fmod.com/t/radom-crash-in-fmod/12988>\
**Category:** FMOD Studio\
**Created:** [February 18, 2017, 1:55am UTC](https://qa.fmod.com/t/radom-crash-in-fmod/12988 "2017-02-18T01:55:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![happybooming](https://avatars.discourse-cdn.com/v4/letter/h/d78d45/32.png) [@happybooming](https://qa.fmod.com/u/happybooming)\
**Post date:** [February 18, 2017, 1:55am UTC](https://qa.fmod.com/t/radom-crash-in-fmod/12988/1 "2017-02-18T01:55:45Z")

</div>

We use compiled fmod studio from the src “fmodstudiosrc\_10810” in our game.  
And we met random crash in fmod with the call stack:

> xx.exe!FMOD::EventInstanceContainer::~EventInstanceContainer(void)   
> xx.exe!FMOD::BasicRepository\<class FMOD::EventModel,class FMOD::EventInstanceContainer\>::close(void)   
> xx.exe!FMOD::PlaybackSystem::createEventInstance(class FMOD::ID const &,class FMOD::EventInstance \* \*)   
> xx.exe!FMOD::AsyncCommand\_eventDescription\_createInstance::executeMain(class FMOD::RuntimeAPI::Manager \*)   
> xx.exe!FMOD::AsyncManager::executeDirectCommand(struct FMOD::AsyncCommand \*)   
> xx.exe!FMOD::AsyncManager::asyncProcessCommands(void)   
> xxexe!FMOD::AsyncManager::asyncThreadLoop(void)   
> xx.exe!FMOD:🧵:callback(void _)   
> ucrtbase.dll!thread\_start\<unsigned int (\_\_cdecl_)(void \* \_\_ptr64)\>()   
> kernel32.dll!BaseThreadInitThunk() Unknown  
> ntdll.dll!RtlUserThreadStart() Unknown

Any one has any idea to fix it?

---

<div class="post-metadata">

**Author:** ![brett](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/brett/32/261_2.png) [@brett](https://qa.fmod.com/u/brett)\
**Post date:** [February 19, 2017, 11:41pm UTC](https://qa.fmod.com/t/radom-crash-in-fmod/12988/2 "2017-02-19T23:41:10Z")

</div>

Do you use memory or file callbacks? Are they thread safe?

I could recommend trying 1.08.16 as well, there are one or 2 fixes that might be relevant since 1.08.10.