MediaMonkey forum

I previously reported that there was a problem in that the process took a while and the cancel option didn't work. The cancel part of the bug has been resolved as the button has been disabled.

Now the bigger issue is the library maintenance never completes when the "Complete" option is selected. "Quick" works fine.

Mike

It seems to be taking really long so far, so it seems you might be right.

It appears to be stuck in a loop... I'm not sure what (if any) tools there are to monitor activity on a SQLite database but I have been capturing snapshots of the journal files. What little I can read in the file seems to be repeating.

I am able to finish it here, it took between 5 and 10 minutes for a database that is about 34 MB.

It did eventually finish here on a 25MB database.

Ok, I'll try again and let it go to see what happens... my database is over 200MB so it may be a while. I'll let you know once it completes (or I give up).

Guess patience is a virtue, huh? It took just over 1 hour to complete.

Wow 1h seems excessively long.

Last time I did the complete optimization it took almost 4 hours...

Yeah, even though it finally completed, there's definitely something wrong here.

MDominik13 wrote:Yeah, even though it finally completed, there's definitely something wrong here.

vpsaxman wrote:Last time I did the complete optimization it took almost 4 hours...

Dreadlau wrote:Wow 1h seems excessively long.

I don't know, did you see the tooltip?

But it never took this long in MM3, so it does seem something has changed.

No, I didn't see the tooltip. Was it in MM3 as well? As Lowlander pointed out, it never took this long for me in MM3. Pretty much the same database took several minutes but not hours.

MDominik13 wrote:No, I didn't see the tooltip. Was it in MM3 as well? As Lowlander pointed out, it never took this long for me in MM3. Pretty much the same database took several minutes but not hours.

When complete optimizing is performed then there is re-created also the full-text search index for each song, this was added in MM 3.1 and can take quite a lot of time.
You can run DbgView and if you will see instant "INSERT INTO SongText .... " SQL queries then it is the full-text search index recreating.

I'll try that to see what's going on. I definitely ran the full optimization in 3.1 and it didn't take this long.