Note that I also faced this same error recently with 3018, so this user is not alone. The issue is that it is a sporadic error. It does always happen though.
Unfortunately, it appears the trend lately is if it is not reproducible with direct steps, don't bother fixing it.
Actually, we do try to fix such issues; in cases such as this, where we're unable to replicate a problem, we ask for the crash log ID and/or a debug log which hopefully reveals where the issue lies.
In this case, the devs will start by checking out the crashlog ID that was provided. If it occurs again, please share the crashlog ID again. And a debug log can provide additional info for the dev team.
lindholm wrote: ↑Thu May 02, 2024 2:04 am
Given that it takes several days for this to happen, collecting a log with Dbgview is not practical.
I agree completely. Only thing I can think of s that there is some memory leak causing MM to crash after several days.
ATM for next few builds we are planning to improve stability and make specific changes to fetch such cases.
EDIT: Have you tried to change output to Direct sound and or disable Exclusive access to sound card driver? Also I am curious what sound card you use to listen music in MM and its driver version.
Yeah, 3022 was an internal build that introduced a regression. We're still working on a couple of stability fixes before we post the beta (hopefully over the weekend).