Very Heavy Processor Usage

mdhmdh31 · Post by **mdhmdh31** » Tue Sep 13, 2005 10:22 am

Good Day -

MediaMonkey is creating a very heavy processor load: 92 - 98% of processor load in use all the time. It's a recent install, but it has been running near 100% of the processor for over 10 hours. I left it the computer on overnight with only MediaMonkey running to see if it would complete whatever it was working on, but it didn't help.

My machine is an AMD Athlon64 Barton 3000+ with 2GB RAM. I have ~60GB of music in 14,000 files. All files are located on a local SATA hard drive partitioned with the Operating System (WinXP, SP2) and programs (incl. MM) on the C:\ partition and the data files (alll the music) on D:\.

When I exit MM the window closes, but the process stays in the task list and continues to use all the processor. If I open a second instance of MM, those two MM processes fight to fill all the processor cycles.

I have already tried uninstalling and re-installing MM, and that did not fix the problem.

Any idea what is going on?

Thanks,
David

mdhmdh31 · Post by **mdhmdh31** » Wed Sep 14, 2005 3:34 pm

After continued research, more information:

If after starting MM, I manually rescan (File-Add/Rescan), the processor sometimes stops racing after it finishes this scan.

Seeing that, I tried turning on "File Monitor" to see fi the autoscanning would bring the same solution, but it did not. After starting MM and waiting for File Monitor to rescan everything, the processor still raced.

Help?
Thanks,
David

Post by **jiri** » Wed Sep 14, 2005 3:46 pm

So CPU is always at 100% until you start a rescan and it finishes? If so, you can try to generate a debug log (http://www.mediamonkey.com/forum/viewtopic.php?t=69) and e-mail it to me.

Jiri

rws7au · Post by **rws7au** » Sat Oct 01, 2005 3:34 am

I am using 2.4.2.874 and also found that after closing MM the CPU is running at close to 100%. The task manager shows Mediamonkey.exe is still running as a process. I trided uninstalling and reinstalling without success. I eventually uninstalled MM. deleted all the library files and searched the PC for any traces of MM related files and deleted them (prefetch files). Did a fresh reinstall and it's working OK at the moment (1 day).

Guest · Post by **Guest** » Tue Oct 11, 2005 8:21 pm

I'm having this *exact* issue...the process stays running @ 100% CPU after I properly quit MediaMonkey.

Do you want a debug log on this, or, would prefer I attempt to replicate with the latest alpha?

rovingcowboy · Post by **rovingcowboy** » Tue Oct 11, 2005 8:32 pm

this is strange as i have seen the same thing but only after i was messing with the computer doing something else while monkey was playing songs and then i made it crash monkey. i had then brought up the task manager and monkey was listed in it so i selected monkey and ended task. on it.

then opened the task manager again to close some other programs to try and get some ram back and seen monkey was still listed there.

could this be part of the memory leek trouble you posted about in the other thread jiri?

if so it has been there since the last released version, because that is the version i am using.

but i am also using a ram cleaner and just might never have seen the trouble because it keeps the ram free.

trixmoto · Post by **trixmoto** » Wed Oct 12, 2005 3:45 am

Unfortunately I cannot replicate this. I have a terrible computer that just about manages to run XP on a good day, and MM runs perfectly with a CPU load of about 10-20. It also leaves task manager when closed.

Are you doing lots of property changes? Is there a message saying "Tagging # tracks" (or words to that effect) in the bottom right hand corner? What player are you using?

Sunspot42 · Post by **Sunspot42** » Sun Oct 23, 2005 4:46 pm

rws7au wrote:I am using 2.4.2.874 and also found that after closing MM the CPU is running at close to 100%. The task manager shows Mediamonkey.exe is still running as a process. I trided uninstalling and reinstalling without success. I eventually uninstalled MM. deleted all the library files and searched the PC for any traces of MM related files and deleted them (prefetch files). Did a fresh reinstall and it's working OK at the moment (1 day).

I'm having the same problem. Did everything you did, except deleting the "prefetch" files. I'm still having the problem. What are the "prefetch" files, and where can I find them?

Thanks!

AMG · Post by **AMG** » Sun Oct 23, 2005 6:59 pm

Any thoughts on this...? Any info I can help gather to track this down? It's very real...

rovingcowboy · Post by **rovingcowboy** » Sun Oct 23, 2005 10:08 pm

sunspot42.

prefetch files are saved in a folder by the operation system.

but the only way i can remember off had to clear them is to get a program that is a tweaking program. the best one for windows stop being free at version 6.

so go to http://www.majorgeeks.com and look for "Xteq Setup 6 pro" that is the last free version of that program and it will blow your mind as to what you can tweak with it.

in there you can find options to set the preftech files to bedeleted on reboots so they are always deleted and you can also find options to make them never get used in the first place.

every one running windows os's should use this program for tweaking it will make your system run the way it is to run if you know how to set up the proper tweaks. don't worry if you can not program or have never used tweaking programs before.

this has wizards for the newbies to use and it will warn you that what you tried to do might hurt your system if you tried to do the wrong thing or something that you wanted but might not be as safe as you thought.

i have been using this xteq program for 6 years now. on all the computers i have believe me you WANT this tweaking program.

you are able to download tons upon tons of user created programs to tweak just about any other program that runs on windows and tons of game tweaks. where you don't even have to use the codes doing the game as this already has them started when the game starts.

cool

for you scripters or programers out there it has a sdk program too and you can add all the plugins you can think of.

rovingcowboy · Post by **rovingcowboy** » Sun Oct 23, 2005 10:15 pm

AMG wrote:Any thoughts on this...? Any info I can help gather to track this down? It's very real...

as for tweaking my systems i still only get this on my win98 system.

so it might be only on the win9x os's. which all have motherboard controled resource ram chips.

windows xp uses the ram sticks for its resource ram.

that is the only thing i can think of which is why i think it is part of that small memory leak that shows up some times as it did in my win 98 the other day.

Sunspot42 · Post by **Sunspot42** » Mon Oct 24, 2005 2:11 am

rovingcowboy wrote:as for tweaking my systems i still only get this on my win98 system.

so it might be only on the win9x os's. which all have motherboard controled resource ram chips.

Nope. I'm running XP Pro, Service Pack 2. It's not just Win9x.

rovingcowboy · Post by **rovingcowboy** » Mon Oct 24, 2005 9:35 am

i don't remember seeing this on my winxp computer?

what hardware are you using amd or intel? it might be one of those at fault or something else you have on that system that is the cause.

i have intel but i don't get this error or not that i noticed before wait a minute i have been noticeing the dsp plugin takes its time in closing after media monkey is closed on this xp. i wonder if it is closing the same time monkey is closing?

if it is then that would make monkey closing about 10 seconds after the icon has been removed from the system tray.

that sound like anything to help you track the error?

AMG · Post by **AMG** » Mon Oct 24, 2005 9:00 pm

The process isn't stopping properly for (whatever) reason. It's highly unlikely this is hardware or OS related. It's extremely likely that an unhandled event is looping (thus the processor spike and the app. not quitting).

I don't know what MM does on it's way "out" (i.e. after you give it the command to exit).

This one is going to be fixed by running a debug build or if the app has some kind of logging capabilities, to enable it.

I 'spose it's not worth worrying about...unless it keeps up after 2.5 is gold...

Post by **jiri** » Tue Oct 25, 2005 2:02 am

As I wrote few posts above, you can e-mail me a debug log in case you can reproduce any strange behaviour.

Jiri