Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[michel]

Without playing anything:

Mega-ME (PixOS):  50-60% CPU
Mega-ME (skin disabled): 50-60 % CPU

if MC is iconified: less than 10% CPU

Mini-ME: less than 10%

What MC is doing ?

Since I pulled a few builds (I was travelling) I am not able to say in which build this problem appeared.

(I have a Duron 700, may be you will be not able to detect that if you have a powerful CPU).

[JimH]

Michel,
Something else must be going on.  Visualization?  Thumbnailing?

Virus scanner?

On XP Home, my cpu is at 0 to 8%, with or without MC with PixOS open.

Jim

[michel]

- Visualization: no
- Playing: no
- Thumbnailing: it is currently in 'list' mode (and I just checked the thumbnail directory: nothing seems to change)

- Virus scanner: I am not talking about global CPU usage but about MC CPU usage (as shown by Task Manager) so...

The main point: MC CPU usage becomes 0% when it is minimized and returns to more than 50% when the windows is restored.

[MidPack]

Checked mine, usage was less than 10% with a playlist going and surfing the internet...

[KingSparta]

>> Checked mine, usage was less than 10%
Mine was between 0% and 1% (Playing Web Stream)

[michel]

Mine is about 5% playing a song... if it is minimized (in the tray). It grows up to 50-60% if it is maximized.

Very strange.

[michel]

I just read that it could be performance issues in some cases after one of the latest windows XP SP1 security patch (it is admited by MS). I don't know if that could be related to my current problem but I can say it is the first time I see such a CPU load using MC (doing nothing).

[michel]

It is related with my library. Switching to another library the problem disapears. There is no problem on the client side using this library through Media Server though.

More information: removing cover art ('inside file') from songs decreases MJ cpu usage a lot during the operation (but it returns to 60% when the tagging operation is finished).

[michel]

I finally found the cause of the problem:

when the 'drop target' bar is set to 'playlist/recently imported' cpu usage is very important.

I switched it to 'play' and cpu usage drop down immediately !

I have to say that my 'recently imported' playlist is 28000 files large but I don't undestand what MC is doing with it to take so many cpu usage when it is in the 'drop target'.

[zevele10]

I have to say that my 'recently imported' playlist is 28000 files large -=-=-=

Thank you my good Zev !

[michel]

N'exagère pas, j'en avais largement plus de 20000 avant que "thank you zev". Le "recently imported" c'est parce que j'ai recréé une lib il y a quelques mois.

[zevele10]

I was joking my friend.
You did not get more than a few thousands from me.
No more than 4 or 5 thousands

[Matt]

Good find.  It'll be a quick fix.