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.

+8 votes
We are in the process of upgrading from the unreal Wwise integration 2021.1.3.7665.2079 to 2021.1.4.7707.2130.

However this has introduced many warnings during cooking saying "LogAkAudio: Warning: Freeing media memory because parent asset was destroyed".
Since we have a zero warning policy this is causing this to fail our pre-checkin checks, and I have been asked to confirm why this warning has been added.

This UE_LOG Warning was added to UAkMediaAssetData::IsReadyForFinishDestroy() as part of the changes to the newer version, and looks to be warning of a potential memory leak.

However we are not doing anything special as far as I can see, so can you advise us on how we can prevent this warning from occurring?
Is it actually as a result of a memory leak which has been caught, or alternatively is that warning just for information and this is the intended data flow?
in General Discussion by DAve S. (190 points)
Hey Dave, just wondering if you ever found a cause/fix for this (or did you simply downgrade the UE_LOG Warning to a Log/Verbose)?
Hi James,

Currently we have removed the warning and opened a ticket.
This is in the system as WG-56935, if you wanted to look out for it in future release notes.
This wasn't fixed at all, running into this with 2021.1.9

Please sign-in or register to answer this question.

...