Description

When PIE'ing and stopping PIE with Google Resonance in use, the engine crashes after PIE session ended.

Crash appears as a result of the Soundfield Submix's Soundfield Encoding Format being set to Resonance Binaural Spatialization and being added to the Ambix Sound Wave's Submix category. 

Reported and tested in version 4.25.3(CL 13942748). 

Steps to Reproduce
  1. Open attached project
  2. Start PIE
  3. Close PIE by pressing ESC or the "stop key".

Result: Engine crash.

Expected: No crash, return to normal editor behavior after PIE has been finished.

Callstack

ntdll!f6de0000  + 9c0f4
KERNELBASE!f3d60000  + 38a83
UE4Editor-Core!ReportCrash(_EXCEPTION_POINTERS *) [WindowsPlatformCrashContext.cpp:1488]
UE4Editor!`GuardedMainWrapper'::`1'::filt$0  [LaunchWindows.cpp:140]
VCRUNTIME140!e4170000  + dfc0
ntdll!f6de0000  + a11cf
ntdll!f6de0000  + 6a209
ntdll!f6de0000  + 9fe3e
 
 
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION 0x00000000
 
UE4Editor_ResonanceAudio
UE4Editor_AudioMixer
UE4Editor_AudioMixer
UE4Editor_AudioMixer
UE4Editor_AudioMixer
UE4Editor_AudioMixer
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Niagara
UE4Editor_Niagara
UE4Editor_Niagara
UE4Editor_Niagara
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Niagara
UE4Editor_Niagara
UE4Editor_Niagara
UE4Editor_Niagara
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Niagara
UE4Editor_Niagara
UE4Editor_Niagara
UE4Editor_Niagara
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_Engine
UE4Editor_CoreUObject
UE4Editor_CoreUObject
UE4Editor_CoreUObject
UE4Editor_CoreUObject
UE4Editor_UnrealEd
UE4Editor_UnrealEd
UE4Editor_UnrealEd
UE4Editor
UE4Editor
UE4Editor
UE4Editor
UE4Editor
kernel32
ntdll

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-99850 in the post.

1
Login to Vote

Fixed
ComponentUE - Audio
Affects Versions4.25.3
Target Fix4.26
Fix Commit14484150
Release Commit14484150
CreatedSep 17, 2020
ResolvedOct 13, 2020
UpdatedApr 28, 2021
View Jira Issue