MediaMonkey forum

I am experiencing this same problem, with build 1251. I had upgraded to 3.1.0.1251 from the official 3.0.7.1191 release in an attempt to address the podcast/wininet #126 problem.

I'm on Windows Vista Business SP2, with IE8. I too have a shared network database (my MM.DB is on a network share and two computers access it), and my library has over 10000 items.

At startup, MM hangs while monitoring, freezing at "Monitoring at 684 of 723 (\\[Network Path]\2005 04.m3u)", which is a playlist. Subsequent reloads always hang at this same spot.

"Terminating" the hung monitoring results in multiple error message dialog boxes showing "Access violation at address 007DAA04 in module 'MediaMokey.exe'. Read of address 00000008". Had to kill the app using task manager.

MM fully hangs, or just the scanning thread freezes and MM continues to work? You can e-mail me a debug log of this, just to be sure what's going on...

Jiri

Only the monitoring hangs, the rest of MM works (although sluggishly). I upgraded to the latest build, 1152, and still had the problem. Thinking this may be a problem with reading certain m3u playlists, I temporarily moved all of my existing *.m3u playlists out of the folders being monitored, then restarted MM. That fixed the issue.

I then exited MM, moved my M3U files back into the folders being monitored, and restarted MM which started the startup file monitoring. Voila, it hangs again (this time on a different M3U playlist). I also note that "Now Playing: Reading Tracks" was taking a VERY long time, but did eventually complete after a few minutes.

These M3U files, BTW, were created by WMP 11 - I had converted and saved my WPL WMP playlists as M3U. I can send you the M3U files if you want to have a look or try it.

I don't have the debug version of 1152 installed, let me know if you need me to do this and send you the log. Feel free to email me directly.

Ok, replied over e-mail.

Jiri

Just to say that the last 4 builds solved the issue for me. BTW I had reverted back to 32 bit due to drivers fr another device, and had the same problem, so it had nothing to do with 64 bit windows 7. Works like a dream now though!