Author Topic: Issue with MB freezing on launch & close  (Read 1297 times)

Mr. Trev

  • Sr. Member
  • ****
  • Posts: 461
Hi. This is a problem I've been having for quite a while (since I got a new Win 10 laptop last summer, MB versions going back to 3.0).

Occasionally when I close MB, even though the program appears to shut down, it'll still be running in the task manager (no CPU usage, just using RAM). If this happens then MB will freeze the next time I try to launch.

Another thing I've noticed that will make MB freeze on launch is when I'm using an external DAC (Fiio X3, ASIO).
If I close MB with the player setting still on ASIO, and try to launch MB without the device plugged in I'll get a freeze (the freezing always happens after the GUI is loaded, BTW). The only way I can get MB to launch again is to plug the X3 back in.

I'm not sure if this should be reported as a bug since I can't 100% replicate things and I also can't say this problem doesn't lay elsewhere - I have MB 3.0 running on my other laptop (Win 7) and don't seem to have these problems there.

I guess what I'm looking for is if anybody can offer a way that I could trace these freezing episodes and find out what's causing the problem

Cheers

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34420
Occasionally when I close MB, even though the program appears to shut down, it'll still be running in the task manager (no CPU usage, just using RAM). If this happens then MB will freeze the next time I try to launch.
On my previous PC i randomly had the same issue. I did a lot of debugging on it and concluded it was an issue with windows and/or .NET - MB itself had completed the final exit point in the code. Unfortunately i wasnt able to change anything that helped.
Since my new PC i have never had any issues with that, and unfortunately i cant really offer any help

Mr. Trev

  • Sr. Member
  • ****
  • Posts: 461
The "hanging task" hasn't been much of an issue for me lately either (I just did yet another clean install)

The ASIO device thing on the other hand happens quite often, since that's how I listen. Most recently happened this morning, and my laptop was completely shutdown last night after I finished my listening session. Maybe the solution there is to use WASAPI instead and hope MB will be more forgiving when the device isn't found (my problem with WASAPI: I just can't get it running in event mode without a ton of background noise)