we’re experiencing a deadlock in the editor after changing some looping sounds to use virtualisation (virtualize) and limit the number of playing events.
macOS 10.15.6, FMOD 2.00.11 and 2.00.12, Unity 2019.4.7.
The first time the Unity editor is played everything works as expected. When we stop and start playmode again the editor deadlocks and has to be force quit. FMOD in the editor is the cause of the deadlock.
When the first play is started the following message appears in the console when the scene starts;
[FMOD] DSPJobList::addJob : DSP JobList expanding job from 1024 entries to 2048 entries.
And when the first play is stopped the following message appears in the console;
[FMOD] OutputRingBuffer::read : Buffer starvation detected, requested 2048 bytes, 0 / 16384 bytes available.
After that, any attempt to play again in the editor causes a deadlock. If I remove virtualisation everything works fine.
Any suggestions for a fix/workaround apart from ‘don’t use virtualisation’? Is there a config somewhere to hint for more allocations?