Trying to solve the problem, I uninstalled 2.4 and went back to 2.3. Same problem, though slightly lower processor usage (80% vs. 95%). Then, I uninstalled that and went to the 2.5.913beta1. This most recent version fixes the problem.

Does experience so far suggest that this beta version is stable for old features (e.g. iRiver, not iPod)?

Thanks again,
David

Jiri -

Another, slightly different look. This one was produced by telling MM to quit before it had finished monitoring my files. Same result from the user perspective: full processor usage with GUI closed but MM still running in TaskMon.

Final lines in the log:
00004061 13.91948318 [1188] We were asked to finish.
00004062 13.91953468 [1188] We are really going to finish.
00004063 13.95599365 [1188] Playback stopped.
00004064 13.95607948 [1188] Forms: Received WM_ACTIVATEAPP
00004065 13.95611763 [1188] Forms: Accepted WM_ACTIVATEAPP -
00004066 13.95629025 [1188] Forms: NormalizeTopMosts: Level: 0
00004067 13.95632553 [1188] Winamp sim - ignoring.
00004068 13.95635509 [1188] Winamp simulation window received messsage 28
00004069 13.96595287 [1188] Winamp sim - ignoring.
00004070 13.96778393 [1188] Terminating device handlers.
00004071 13.96984959 [1188] Terminate auto-scanning.
00004072 13.97452259 [1188] Clear songlist.
00004073 13.97457314 [1188] Terminate all threads.
00004074 13.97460175 [1188] Termination of all threads started.
00004075 13.97463417 [1188] There is currently 3 threads running.
00004076 13.97472095 [1188] All threads were asked to terminate.
00004077 13.98563480 [1188] 3136 DB lock finished, took 267916.
00004078 14.84769821 [1188] Going to make final callback 3136
00004079 14.95978737 [1188] Thread has finished 3136
00004080 18.29039001 [1188] MP3: Tag read from D:\_Music\Quotes\A Few Good Men (Cruise & Nicholson)-A Few Good Men.mp3
00004081 18.29386902 [1188] MP3: Going to read tag from D:\_Music\Quotes\I Rule (Kevin Spacey)-American Beauty.mp3
00004082 18.29399109 [1188] MP3: Tag read from D:\_Music\Quotes\I Rule (Kevin Spacey)-American Beauty.mp3

... 12X more Going to read -- Tag Read

00004105 58.29535675 [1188] MP3: Going to read tag from D:\_Music\Quotes\Fava Beans and a Nice Chianti (Anthony Hopkins)-The Silence of the Lambs.mp3
00004106 63.29290390 [1188] MP3: Tag read from D:\_Music\Quotes\Fava Beans and a Nice Chianti (Anthony Hopkins)-The Silence of the Lambs.mp3
00004107 63.29294968 [1188] Winamp's playlist scanning finished.
00004108 63.29300690 [1188] Going to make final callback 2856
00004109 63.29332352 [1188] Thread has finished 2856

jiri wrote: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

Jiri - I apologize for the delay. I just sent you an E-mail with the log attached. (I failed to look at the size first, so it's pretty big with all the scan info.) As a layman, it looks pretty normal to me until the end. After I tell MM to quit, the MM GUI window does shut down, but the process is still running at high processor usage. Task Monitor shows it as variable between 70 and 85% processor usage (because I have some other processes running as well). It doesn’t stop unless I manually kill it in TaskMon. The final log lines are:

00015645 166.67018127 [3760] Starting a new Winamp's scanning thread.
00015646 169.59190369 [3760] We were asked to finish.
00015647 169.59194946 [3760] We are really going to finish.
00015648 169.63467407 [3760] Playback stopped.
00015649 169.63476563 [3760] Forms: Received WM_ACTIVATEAPP
00015650 169.63482666 [3760] Forms: Accepted WM_ACTIVATEAPP -
00015651 169.63485718 [3760] Forms: NormalizeTopMosts: Level: 0
00015652 169.63504028 [3760] Winamp sim - ignoring.
00015653 169.63508606 [3760] Winamp simulation window received messsage 28
00015654 169.63511658 [3760] Winamp sim - ignoring.
00015655 169.64923096 [3760] Terminating device handlers.
00015656 169.65345764 [3760] Terminate auto-scanning.
00015657 169.65620422 [3760] Clear songlist.
00015658 169.69137573 [3760] Terminate all threads.
00015659 169.69143677 [3760] Termination of all threads started.
00015660 169.69158936 [3760] There is currently 1 threads running.
00015661 169.69161987 [3760] All threads were asked to terminate.
00015662 171.63047791 [3760] Thread has started 2740
00015663 171.63061523 [3760] Thread is not allowed to start 2740

Good luck hunting to squash this thing.
Thanks very much for the help,
David

My sincerest apologies...I had submitted a debug log, and, received an e-mail with some questions...unfortunately, that e-mail has been misplaced. However, from what I recall...

Does this occur if you clear your "Now Playing" list? No, if I clear the Now Playing list this does not occur on exit of MM.

try going to the options panel and setting the background functions to

lower.

then when you rip, convert, analyize, the songs you can right click on the status bar and adjust the priority in there to the highest and it will run for that operation only and when it is finished it goes back to normal.

that seems to keep the cpu in the proper useage as it always closes the highest priority and resets it back to normal.

i think it is just like manualy turning the switch off all the time. not sure but it seems to work like that for me.

You can set MM background process priority to a lower value and it should then not drain all your processor. Of course I prefer to have MM running as close to 100% as possible when it is ripping a CD because it finishes quicker!

Hi,

Actually I didn't notice the MM's heavy memory usage not until i try running the rip audio CD. As soon as the process just started, my CPU is already boosted to 100%, i can feel my laptop is boiling. Eventually it just shut off by itself. (within few minutes). To clarify, I had minimize all the CPU usage by shutting down all other unused process to make sure it is not caused by overloads.

I have a laptop of Mobile AMD Athlon XP-M 2200 w/PowerNow , WinXP Home, 512MB RAM.

MM is a good media player, but those backgroud process really KILLs lot of CPU usage Anyone knows how to limit MM memusage or using WinXp's app to restrict the process mem usage??

Help.....

Jiri,

Thanks for your patience...you did indeed post that and I completely missed it. I'll get a debug log genereated and sent to you right away!

Check out top of this forum, namely http://www.mediamonkey.com/forum/viewtopic.php?t=69.

Jiri

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

Jiri

Would love to, thanks. Where does one find this debug log?

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

Jiri

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...

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?

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.

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.