Domain reload stuck when using multiple audio APIs - IN-82349

I’ve been struggling with an issue for a while now, and have somewhat recently been able to get a really simple repro project put together.

Basically, after making code changes, the editor will get infinitely stuck in domain reload, and Task Manager shows essentially zero CPU activity in the Unity processes, which suggests some kind of threading deadlock.

The only thing I have been able to pinpoint with this bug is that it only seems to happen when I use multiple audio APIs. In projects where I don’t touch audio, it never happens. And in projects where I only use procedural audio, it also never happens. Yet if I try to isolate the specific APIs that seem to trigger the issue the most, the issue doesn’t reproduce as easily. So it seems it is some combination of APIs that cause it to get stuck.

Bug is IN-82349 and I’ve attached a video in the report showing the domain reload getting stuck. The previous time I reported the bug, it was confirmed, and then closed because someone believed it was fixed with Burst 1.8.17. But as the video shows, I have been able to reproduce it with the newer Burst version.

2 Likes

Thanks for resubmitting. I’ll try and shuffle it forward to us on audio team. I couldn’t repro on mac, but triggering a domain reload whilst in playmode causes a hard crash. Seems like lots of moving parts in this - burst, custom ECS, DSPgraph, custom blobbing, domain reload. fun!

1 Like