MediaMonkey forum

Great! Thanks for confirming!

-Rusty

This problem just started happening to me running version .3113

Hi,
Try latest viewtopic.php?t=86639&sd=d it should be fixed.

Hey version .3152 seems to have resolved my issue - thanks!

This bug has come back for me on latest build (3153)

I have had this happen only a couple of times over the 10 or so versions. A total hang is far less prevalent than several months ago. Will run debug and generate a log if it hangs again.
Matt

It's possibly due to MediaMonkey not having closed all process on last exit. If true a debug log capturing closing would be more helpful.

You can check the Task Manager's Details tab to see if any MediaMonkey processes are still running prior to launch and stop any that are still showing after MediaMonkey close.

3153 debug
The problem is recurring again for me as well. There is definitely nothing left over after previous close. It seems to be related to looking up the CD online – if the CD is not found the problem was much more prevalent. I have a log now of it happening a handful of times and will try to attach it to ticket #21491…

Hi,
I dl'd MM 2024.2.0.3155 to see if it would solve my problem with the hanging at the splash screen. It worked the first few times, (3 or 4) but it now it is hanging again. When it did work, it took a long time (like 3-5 minutes) to load. Hopefully there is a solution forthcoming as it is rather frustrating that I can't use MM atm.

This is my machine:
Processor Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz 3.40 GHz
Installed RAM 16.0 GB
Storage 3.64 TB HDD ST4000DM005-2DP166, 466 GB WDC WD5000AAKS-00A7B0
Graphics Card AMD Radeon HD 7500 Series (1009 MB)
System Type 64-bit operating system, x64-based processor

When it hangs, are there unclosed MediaMonkey processes from previous runs in Task Manager?

Please capture the failure to launch as well as the slow launch in separate debug logs (step 4b) and attach the logs to a Support Ticket: viewtopic.php?t=86643

This will help a developer analyze why this happens on your setup.

Ticket #11493: "Hanging on Splash Screen" has been successfully submitted. I am unable to get MMW to load, so I cannot submit a script for that scenario.

I too have experienced "hanging on splash screen" since 3082 (currently using 3155 debug). It occurs intermittently; I've been trying to identify the conditions on my PC (Windows 10) that cause the hang. It seems to occur the first time I start mediamonkey after a reboot, but not always. It hangs with a single mediamonkey process of about 30MB and requires "endtask" to kill it. Afterwards, mediamonkey starts normally . . . It does not appear to generate a debug file, so I tried running dbgview first, and mediamonkey always starts if dbgview is running . . . seems to be a timing issue?

The new build (not available yet) will have a fix related to this. In the meanwhile you can either wait for it and test that or capture the failure to launch in a debug log (step 4b) and attach the log to a Support Ticket: viewtopic.php?t=86643

This happens to me routinely, as reported above. It is problematic for me because I am frequently having to restart MM from a rebooted computer, and MM typically freezes the first time around. The biggest problem is that it can take some time (10s of seconds) before it becomes apparent that MM has failed to load.

What I do now if I suspect that it has frozen is to fire up the DbgView event recorder (described in the "how to report a bug" threads) . If DbgView does not report a reasonably active stream of new events then MM has frozen.

If MM has frozen, the thing to do is fire up the Windows Task Manager (CTRL+ALT+DEL), scroll down to the Background Processes section, select the "MediaMonkey 2024 (32 bit)" entry (alphabetic order) and use the End Task button to terminate MM. After a couple of seconds fire up MM again and it should work. If not, just repeat - it has not failed to start for me on the third attempt.

Cheers
Matt

Froze again with v3162 debug. First fire up of the day, no hanging processes from previous launch. Unfortunately not running dbgview, so no log.
Started quickly after termination of the MM process in Task Manager.