thanks, downloaded 1.0.2.29 and ticked the show icon box. Seems to work fine now.

s-dot wrote:This still happens for me with the latest scrobber version installed. (1.0.2.26) on VISTA 64 bit version. However, keeping 'show last.fm toolbar icon' unticked in the options will keep the cpu usage down.

1.0.2.26 is not the latest, you want 1.0.2.29.

Stumbled over this post while looking for a solution to the problem above. I run mediamonkey 3.2.3.1302.

This still happens for me with the latest scrobber version installed. (1.0.2.26) on VISTA 64 bit version. However, keeping 'show last.fm toolbar icon' unticked in the options will keep the cpu usage down.

I wonder if the last fm problem also causes the audio library to not being liked and closed by data execution prevention (or whatever the exact name is) occasionally.

now it is "kind of" fixed. for me the cpu usage won't go up that high anymore but sometimes it rises still up to 40-50%.

It should be Fixed in Last.fm 1.0.2.29 along with few other tweaks.

In case you encounter any issues please let us know ASAP as we are determent to fix that.

finally! thank you. hopefully it will be fixed

Tracked at: http://www.ventismedia.com/mantis/view.php?id=7942

-Rusty

Still happening in 1391 with 2.26
Only if MM is open for a number of hours. Eventually will use 100% of CPU and stop scrobbling going forward.

One more reason that it's scrobbler is that after I uninstalled it, the problem went away

i believe it is the scrobbler because it also happens when you use the scrobbler in MM3.

Still happening for me with 1388 and and the .26 version of the scrobbler plugin. I think I'm using the default settings of the scrobbler plugin, bug reliably occurs at the end of any track, whether it's to be scrobbled or not. Also my last.fm profile page isn't getting the Now Playing info. Just in case it makes any difference I'm using portable MM4 installation.

stan9980

Yep I'm having that problem with MM 1385 too. I use Last FM service and Last FM node. If Last FM Service is activated then when the first track has finished playing the CPU shoots up and stays up. Also this creates an error message on exit.

If I disable FM service and restart MM and just use FM Node then cpu use remains minimal. Also the log in FM service looks funny but can't remember exactly what it used to look like?

So problem with the beta and FM Service I would say

I reported this issue previously in the last.fm thread, if you allowed mediamonkey to finish playing a song while audioscrobbling was active (eg. Green or Yellow status), it would spike CPU until exit or closing the gen_scrobbler DLL thread. I'll look into this a bit more as well

I have seen this in previous builds and versions of the last.fm scrobbler. The high cpu usage would be triggered at the end of a track/podcast and exiting MM4 would be the only solution. Cpu usage would remain high if I didn't.

I haven't had a chance to test the lastest build and scrobbler version. I'll report back when I have.

stan9980

PS> Last version is 1.0.2.26.