Ok, thanks.

This is why I am hesitant to create Mantis tickets of my own issues. With your help to troubleshoot this I was able to determine that it was my system and not MM that was causing the issues. I would rather determine that first before opening tickets.

Nyn

It's script related.

During the filling I see a lot of lines starting with 'Events:...' that are most probably debug lines of a script that could slow things down. Could you test without scripts to be sure it is not script related issue.

Here is a debug log of the access times although with 1399 it is not as bad as it was. http://dl.dropbox.com/u/13254132/ap%20access%20time.LOG

Yes but it is not as bad on a clean db, I think the problem lies with my computer needing some maintenance more than MM. I'm going to do some cleanup this weekend to see if it resolves the issues. I think although I tried a clean db because I have alot of "junk" in my scripts.ini and mediamonkey.ini from mm3 this might be causing some of my issues. I'll let you know if this does not improve things.

Nyn

Nyn, I see here http://www.mediamonkey.com/forum/viewto ... 52#p303071 that you had still some script orphans,
is this problem reproducible with a clean database?

Noted at http://www.ventismedia.com/mantis/view.php?id=6498 -- it seems similar to a couple of other reports re. Auto-playlists _sometimes_ taking a long time to access.

-Rusty

here is a log, it took over 5 minutes for my 18178 music tracks to load but this one didn't loop the playing tracks: http://dl.dropbox.com/u/13254132/mm4%20 ... tracks.LOG

I am at a loss here so I am unable to even figure out how to diagnose this or to reproduce the steps. For some reason, some times it happens when I first open MM, sometimes it happens after MM has been sitting for a long time, sometimes it happens after I have watched videos and sometimes it will not happen during a session at all. But for the last several builds, when I try to access autoplaylists or magic nodes my system will seem to lock up and take several minutes before results are outputted into the track browser and if a track is playing it will lock up and continue in the loop where the last few seconds of the song will continue to play over and over until mm finally releases it. I've tried to reproduce it and produce a debug log but of course when I have debug running and am trying to get it to do it it doesn't. I've done some searches and I do not see anyone mentioning this so I am thinking it has to be something on my machine. Does anyone know of any reasons why or what script could be causing such lockups??

Nyn