Audiokinetic's Community Q&A is the forum where users can ask and answer questions within the Wwise and Strata communities. If you would like to get an answer from Audiokinetic's Technical support team, make sure you use the Support Tickets page.

0 votes

We have received a few reports of crashes from teams that updated to Wwise 2023.1.15 or 2024.1.7. It is related to loading and unloading Rooms and Portals. The call stack of this crash can look like the following:

AkSortedKeyArray<AkSpatialAudioID,AkEdgesByInstance,AkArrayAllocatorNoAlign<10>,AkGetArrayKey<AkSpatialAudioID,AkEdgesByInstance>,AkGrowByPolicy_Proportional,AkTransferMovePolicy<AkEdgesByInstance>,AkDefaultSortedKeyCompare<AkSpatialAudioID> >::Exists()

AkEdgeInstanceSet::Clear()

AkGeometryInstance::UnindexPortalEdgeGeoemtry()

AkAcousticPortal::ClearGeometry()

AkAcousticPortal::~AkAcousticPortal()

AkDynaBlkPool<AkAcousticPortal,64,AkArrayAllocatorAlignedSimd<10> >::Delete()

AkSoundGeometry::DeletePortal()

CAkAudioMgr::ProcessMsgQueue()

AK::JobMgr::Internal::JobBody<<lambda_2aeaa40484afd64b878efc5169e15297>,AK::JobMgr::Job>::Execute()

AK::JobMgr::Internal::JobManager_internalWorkerFunction()

AK::JobMgr::WorkUntilDone()

CAkAudioMgr::Perform()

CAkAudioThread::EventMgrThreadFunc()

We have identified the bug, which will be fixed in Wwise 2023.1.16 and 2024.1.8, which are planned to be released on September 16th and 17th. The bug can also occur in Wwise 2025.1.0 and Wwise 2025.1.1 beta releases; it will be fixed for the 2025.1.2 Beta 3 release. For your reference, the bug is tracked by the WG-79614 Jira; look for this in the release notes to confirm the fix is included.

ago in General Discussion by Guillaume R. (Audiokinetic) (9.3k points)
edited ago by Guillaume R. (Audiokinetic)

Please sign-in or register to answer this question.

...