Clicking on "title" subnode jams MM [#5526]

[Guest]

When I click on the "title" subnode, MM jams up for several minutes and runs my PC at 100%. I have the latest beta version and Windows XP SP2.

[Ludek]

This should not happed, on select the 'Title' node there should be all tracks (that belong to the active filter/library) listed in the tracklist.
It is about 10 000 tracks in my case.

How big is your DB? How many tracks?
Does the same problem occurs when you select "Artist & ALbum Artist" node?

[Guest]

27,000 songs. It jams up for a good 2 minutes.

[Guest]

Nope. This only occurs when I click on the "title" node. All of the others work perfectly.

[Ludek]

Strange, it should do exactly the same as if you click on the "Artist & ALbum Artist", just sort order is different.

Could you generate a debug log using the DbgView app?
- Download the DbgView application from: http://www.microsoft.com/technet/sysint ... gview.mspx
- Execute DbgView.
- Run MediaMonkey and you will see the log being generated to the DbgView app window.
- Save it to a file and upload it by using a free service like RapidShare or YouSendIt.com
- attach the link to the shared file here.

Thank you.

[Bex]

Tried but can't reproduce...

@Guest, try to "File->Maintain Library->Optimize database(Complete)" and see if it helps.

[Guest]

Appreciate the responses. Regarding the post, I am still having the same problem and I will run the debug log when I get back in town. MM also jams up in the same manner anytime I try to rate a song while it's playing. The song continues to play but the system runs at 100% for several and does not respond.

[rusty]

I can't reproduce this either. If you can, please post a debug log (here or via the support desk).

Thx.

-Rusty

[Lowlander]

I can reproduce it, I will try the latest release later and see if it still happens and provide the dbgview log if it does.

[Guest]

That would be great Lowlander!. I am still having that issue but once again do not have access to my computer. I was hoping someone else could reproduce it.

[Lowlander]

I've send a debug log to Ludek, let's hope it gives some insights.

[Ludek]

@Guest

Have you already arrived back to the town? Could you also attach the debug log and also your DB if possible.
Studing the Lownlander's log I found out that this SQL:
SELECT DISTINCT upperw(substr( songtitle, 1, 1)) AS letter
takes the time and makes MM unresponsive, but Lownlander owns 800 MB's DB with 150k tracks, but on your 27k track's DB there should not be such a problem.

[Bex]

I actually could reproduce this once or twice the other day but not anymore?

Anyway, this sql is a bit faster, perhaps fast enough?
SELECT DISTINCT SUBSTR(SongTitle,1,1) COLLATE IUNICODE AS Letter FROM Songs
Simply uppercase the letter in the node caption afterwards instead.

[Lowlander]

If you want to try to reproduce try this when you start MediaMonkey and then expand the Title node. The first time it can take a long while (mine almost took 3 minutes). Any subsequent openings of the Title node are a lot faster due to caching. The effect should also be less pronounced on smaller database files as less data needs to be cached. Furthermore system speed will also play a factor.

[Ludek]

Tracked as
http://www.ventismedia.com/mantis/view.php?id=5526