[1491] Crash after resuming from hibernation

[MichelR]

I almost always send my PC into hibernation rather than shut it down - been doing that for years. Recently MediaMonkey started crashing when resuming from hibernation (I've since installed the debug version, so a couple of crash reports have been sent in). MediaMonkey is usually the only application I leave open when hibernating. This seems to have started somewhere after build 1486 (I'm almost 100% positive that that one wasn't doing that). I know for sure 1489 was crashing - I don't think I ever installed 1487 and 1488 (been a bad week, bear with me... )

Just wondering if this is happening to anyone else. Running Windows 7 64bit, 8Gb of RAM.

[Lowlander]

Create a debug log (step 4b) for this crash and send it to support: http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341

[MichelR]

I thought MediaMonkey had already taken care of it? I got a "message sent" confirmation a couple of times after I sent my initial report through the dialog (the next times it just did it itself). Anyway, I can definitely do that the next time - sometime later today as I don't have time now. Thanks.

[Lowlander]

You may want to add the .elf file mentioned as well (zip log and elf together).

[SansaMonkey]

I can't reproduce such a crash.

What is going on with MM when hibernate ist started?

[MichelR]

You may want to add the .elf file mentioned as well (zip log and elf together).

Just sent in the Dbgview log file (559253). There was no .elf file in the directory, however (most likely because MM does report sending a crash report, I guess that gets erased right after that).

Thanks,
Michel

[MichelR]

I can't reproduce such a crash.

What is going on with MM when hibernate ist started?

It's not doing anything, just sitting there (i.e. no music is playing and no other operation is going on when I send the machine into hibernation). Well, technically it is monitoring some folders on my home network on a Windows Home Server (Acer H340).

[rusty]

Note: This problem is related to interactions between MediaMonkey and a third-party multi-monitor management application called DisplayFusion.

Stopping the application solves the problem.

-Rusty

[MichelR]

I can add that the problem only started after upgrading to DisplayFusion 4.0, recently released.