Build 1292 - MM GUI stops responding

[sugi]

Hello,

lately I keep getting problems when multiple background threads are running. Every now and then MM just stops responding.
You can find a debug log here: http://www.humyo.de/F/9928891-281475013653533
I have also sent a couple of debug logs via the internal functions in the last few hours.
The problem showed up before I installed the beta, I just didn't see the problem often enough to actually care about it, but currently I'm reorganizing my library and seem to run into the problem more often.
I have moved the DB file to the same network drive my music files are on, but ran into the problem severall times before.
There seem to be a couple of factors that favor the problem:
- Monitoring after starting MM still running (takes probably 30 minutes for me, as the music files are on a network share)
- AutoRateAccurate Script is in Phase 2
- Volume analyze background task running
With these three tasks running at the same time, it seems to me that I hit the problem everytime.

Please tell me if you need more informations.

System:
Windows 7 64bit
Intel Core2 Duo 2.6 GHz
4 GByte RAM
1 HDD, 1 TB, around 50% free
1 DVD, 1 DVD-RW
MediaMonkey 3.2.0.1292
Musicfiles and DB are on M:, a network drive on a QNAP NAS

[Owyn]

One thing that can help is NOT running debug mode when you have a big job to do.

I have been doing some fairly hefty maintenance to my database recently and had to stop running debug mode to get things to work in a semi-reasonable manner.

Using the latest beta is also strongly recommended. The MM Appears to be Frozen alerts are much less likely. The timeout involved was increased from 1 minute to 5 minutes in 3.2.

That said, there are still times when the MM UI locks up. I have got to the point when I just sigh and wait for the current operation to complete.

[sugi]

One thing that can help is NOT running debug mode when you have a big job to do.

I have the problem with the normal and the debug build.

Using the latest beta is also strongly recommended. The MM Appears to be Frozen alerts are much less likely. The timeout involved was increased from 1 minute to 5 minutes in 3.2.

The version listed in my post is MediaMonkey 3.2.0.1292. According to the thread above it's the newest build.

That said, there are still times when the MM UI locks up. I have got to the point when I just sigh and wait for the current operation to complete.

I've had it running a whole night (round about 10 hours). That's enough, I assume?

[Owyn]

Ouch. I was talking about minutes, not, hours.

Reading your first post again a big difference between our tests is that I am not running any background processes at the moment. I have even changed Podcast scan to manual. Also working from local internal drive, not a network share.

My comments still stand, but, time to turn this thread over to some one with a closer environment/experience to your own.

[nynaevelan]

I have two observations that relate to my experiences with having the DB on a network. 1. Running Mm on a network is much slower no matter what processes I use and to use more than one at a time brings it to a crawl. I assumed this was due to my hardware so I move MM back to an internal drive. 2. Autorate runs very slow when re-analyzing my entire library when MM is on an internal drive, it is practically unusable when on a network drive.

However, to help you you need to change some things. You should probably turn off startup file monitoring, or do not start playing tracks until after it is complete. You can also change the priority of some tasks so they are not trying to run at the same time. Sometimes tasks will lock themselves up because they do not know who should go first. Volume analyzing is also a GUI intensive process, have that complete by itself as well.

[rusty]

Sugi,

Any scripts running? If yes, does the problem persist after you rename the scripts folder?

Also, is the UI slowness solved by doing the following?
1 open notepad and type 2 characters
2 Copy and paste the 2 characters (in notepad)

I'm asking because we discovered a bug that causes slowness in the MM UI when thousands of tracks are copied to the clipboard.

Thx.

-Rusty

[MJF68]

Could it be that is has to do with Humyo running at the same time as mediamonkey? I had a similar problem, and it is solved when I stop Humyo (including some files that are related to Humyo that don't close when I shut down Humyo)