Community Q&A

Welcome to Audiokinetic’s community-driven Q&A forum. This is the place where Wwise and Strata users help each other out. For direct help from our team, please use the Support Tickets page. To report a bug, use the Bug Report option in the Audiokinetic Launcher. (Note that Bug Reports submitted to the Q&A forum will be rejected. Using our dedicated Bug Report system ensures your report is seen by the right people and has the best chance of being fixed.)

To get the best answers quickly, follow these tips when posting a question:

  • Be Specific: What are you trying to achieve, or what specific issue are you running into?
  • Include Key Details: Include details like your Wwise and game engine versions, operating system, etc.
  • Explain What You've Tried: Let others know what troubleshooting steps you've already taken.
  • Focus on the Facts: Describe the technical facts of your issue. Focusing on the problem helps others find a solution quickly.

Wwise runtime does not reap its threads on shutdown?

0 votes
We're having a rare issue in all of our Windows builds where we'll get an access violation in the XAudio2_7.dll while shutting down.

This only occurs while we're shutting down and, from the times it's been observed, we've already asked the Wwise runtime modules to terminate.

This seemed odd to me, because I confirmed that various Wwise threads (Such as the monitor and event threads) were still alive even though their modules' ::Term functions returned and did not seem to spit anything into the TTY.

I also double-checked that our shutdown sequence is correct, and it lines up with the sequence described in the "Terminate the Different Modules of the Sound Engine" in the SDK docs.

Is the runtime not supposed to reap its threads? What else should I be checking?
in General Discussion by Vitor M. (180 points)

Please sign-in or register to answer this question.

Powered by Question2Answer
...