Binaural Monitor Plugin Crash Mac & Windows

[DrWig]

Mac OS 14.7.4 (M3 Macbook Pro)
Reaper v7.34
EAR: 1.1.0b-EPS

Attempting to open the binaural monitor causes a crash every time in Reaper (after fresh install of reaper and EAR).

However, after trying a few things (changing sampling rate etc.) loading a template project worked fine, and now binaural monitor doesn't crash anymore! Very odd!

Crash report was always this:

Thread 8 Crashed:: */mediaafx
0   libsystem_kernel.dylib        	       0x18c8815d0 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x18c8b9c20 pthread_kill + 288
2   libsystem_c.dylib             	       0x18c7c6a30 abort + 180
3   libc++abi.dylib               	       0x18c870d08 abort_message + 132
4   libc++abi.dylib               	       0x18c860fa4 demangling_terminate_handler() + 320
5   libobjc.A.dylib               	       0x18c4fbc00 _objc_terminate() + 160
6   libc++abi.dylib               	       0x18c8700cc std::__terminate(void (*)()) + 16
7   libc++abi.dylib               	       0x18c873348 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 88
8   libc++abi.dylib               	       0x18c87328c __cxa_throw + 308
9   EAR Binaural Monitoring       	       0x31e6df954 visr::rrl::AudioSignalFlow::process(float const* const*, float* const*, unsigned long, unsigned long) + 1076
10  EAR Binaural Monitoring       	       0x31e6465dc bear::Renderer::process(float const* const*, float const* const*, float const* const*, float* const*) + 168
11  EAR Binaural Monitoring       	       0x31e6540d0 bear::DynamicRendererImpl::process(unsigned long, float const* const*, unsigned long, float const* const*, unsigned long, float const* const*, float* const*) + 720
12  EAR Binaural Monitoring       	       0x31e61aa1c ear::plugin::BinauralMonitoringAudioProcessor::doProcess(float**, unsigned long) + 420
13  EAR Binaural Monitoring       	       0x31e175d5c EarBinauralMonitoringAudioProcessor::processBlock(juce::AudioBuffer<float>&, juce::MidiBuffer&) + 1320
14  EAR Binaural Monitoring       	       0x31e1aaf40 void juce::JuceVST3Component::processAudio<float>(Steinberg::Vst::ProcessData&, juce::Array<float*, juce::DummyCriticalSection, 0>&) + 2392
15  EAR Binaural Monitoring       	       0x31e1a5830 juce::JuceVST3Component::process(Steinberg::Vst::ProcessData&) + 420
16  REAPER                        	       0x1014c279c void VST_HostedPlugin::VST3_Process<float>(float**, float**, int) + 2364
17  REAPER                        	       0x1012fcc88 VST_HostedPlugin::ProcessSamples(int, double*, int, int, int, double, midi_List*, bool*, double, double, double, bool, bool, int, bool) + 7216
18  REAPER                        	       0x10130f8b8 FxDsp::processFxDsp(int, double*, int, int, int, int, double, midi_List*, double, bool, double, double, double, double, int, bool) + 2028
19  REAPER                        	       0x10133d574 FxChain::ProcessChainDsp(FxDsp*, int, FxChain::proc_ctx const*, double*, midi_List*, int, int&, int&) + 420
20  REAPER                        	       0x10133d3ac FxChain::ProcessChainForContext(FxChain::proc_ctx const&, int, double*, midi_List*) + 796
21  REAPER                        	       0x10133e15c FxChain::ProcessChain(int, double*, int, int, int, int, double, midi_List*, double, bool, int) + 2156
22  REAPER                        	       0x1010695fc MediaTrack::RenderSamples_nocache(double, long long, double*, int, int, double, MediaTrack* const*, int, int*, bool, int, int, bool*, SyncSMP_Context*) + 16924
23  REAPER                        	       0x10105fc94 MediaTrack::RenderSamples(double, long long, int, Track_RS_Output*, int, double, MediaTrack* const*, int, midi_List*, int, int, int, int, int, MediaTrack::Track_SendRec*, bool*, SyncSMP_Context*) + 1528
24  REAPER                        	       0x101061210 MediaTrack::RunWorkThread(int, int, double, MediaTrack* const*, int) + 3708
25  REAPER                        	       0x1010b408c WorkerThreadInst::threadProc(void*) + 1832
26  REAPER                        	       0x10149a204 __threadproc(void*) + 32
27  libsystem_pthread.dylib       	       0x18c8b9f94 _pthread_start + 136
28  libsystem_pthread.dylib       	       0x18c8b4d34 thread_start + 8

[DrWig]

On Windows 11 (reaper 7.33) I get a crash if I connect a HOA object to a EAR scene connected to the binarual decoder.

Loading a template with HOA and binaural also crashes reaper (EPS two objects, two stereo beds plus HOA template.rpp)

Faulting application name: reaper.exe, version: 7.3.3.0, time stamp: 0x679fbd84
Faulting module name: EAR Binaural Monitoring.vst3, version: 0.0.0.0, time stamp: 0x65fb0cce
Exception code: 0xc00000fd
Fault offset: 0x00000000003a2da7
Faulting process id: 0x4558
Faulting application start time: 0x1DB9E574E087BF3
Faulting application path: C:\Program Files\REAPER (x64)\reaper.exe
Faulting module path: C:\Program Files\Common Files\VST3\ear-production-suite\EAR Binaural Monitoring.vst3
Report Id: e7770881-371e-49ec-a0a6-d6d049f984e4
Faulting package full name: 
Faulting package-relative application ID: 

[DrWig]

Downgrading EAR Production Suite to v1.0.0 (tested Windows so far) fixes the issue.

[I-AMP]

I encountered the same issue on windows 10 resolved as above by downgrading the EAR production suite to v1.0.0.

Both could be added to a project and functioned correctly individually but as soon as they both were linked to the Scene plug-in reaper crashes.

[firthm01]

Hi @DrWig, @I-AMP
Thank you for raising.
We found a crash bug in the Binaural Monitoring plugin a few months ago which will be resolved in v1.2 (#277). However, looking at that call stack, it looks like this is something different!
We've tagged the v1.2 release at this stage and will probably keep that where it is as we're only awaiting code-signing now, but this probably warrants further investigation for the next.
If you have an RPP you could share, that might save some time in investigation 👍
@rsjbailey - looks like this is probably DSP rather than metadata thread related like the last bug as it fails right down in VISR, but I haven't seen this before in testing. 1.1.0 and 1.1.0b will not make a difference since 'b' only affected the setup app on macos. Need to diff changes between 1.0.0 and 1.1.0.

[DrWig]

On windows, just loading up the template file caused the crash (seems to be related to having both HOA and binaural plugins on windows).

On Mac, just putting the binaural monitor onto a single track (i.e. the first thing I did) caused a crash.

Never got as far as saving an rpp file, but shout if you want me to try anything/reproduce.

One of my students noticed the issue on windows which I confirmed was the same on my win11 system too.

[firthm01]

On windows, just loading up the template file caused the crash (seems to be related to having both HOA and binaural plugins on windows).

Thanks - just tried on a new machine and seeing the same thing. I have something to go off of, hopefully an easy fix 🤞

[firthm01]

Dev notes:

• crash reliably occurs on "EPS two objects, two stereo beds plus HOA template.rpp", tested on fresh machine win 10
• tested REAPER v7.35 and v6.84 (i.e, unlikely to be 64ch vs 128ch changes)

[firthm01]

OK, I've done a bit more investigation and I think as I suspected, we're looking at two bugs here.

The crash I was able to reproduce was #277, which is fixed in the upcoming v1.2.0. I believe this is also the crash @DrWig saw on windows, since "Exception code: 0xc00000fd" is a stack overflow code. I suspect this is also the one @I-AMP has seen.
This bug probably only affects windows as the stack size on that thread is bigger (and probably big enough for the task) on macOS.

The crash in the original post is something different as that callstack is DSP related. I've not been able to reproduce that one yet.

[DrWig]

I can't get my Mac to crash since I opened the template project. I tried clearing my cache and rescanning plugins, but that didn't break it. I'll try harder and report back

[firthm01]

No worries. Sounds like it might be a tricky one so don't worry if you can't find a way to reliably reproduce it. I wonder if it has something to do with REAPER being a fresh install. Maybe it's something along the lines of the audio device never having been opened yet, so we're doing something silly like trying to DSP at 0 sample rate or 0 channels.