MM5 [2832] High CPU Usage

[PoorBoy2001]

With the last few builds I'm experiencing high CPU numbers (between 20-30%) whenever MM is running (even if not playing anything.

It doesn't appear that MM is stuck on any background processes (like syncing or tagging) and is otherwise working normally. A clean re-install didn't solve the problem. I thought it might be OneDrive related, as that app is a CPU hog, but the OneDrive plugin is disable in MM.

Here's a shot of the task manager MM processes: https://1drv.ms/i/s!An5f5Xm0GnulgYKqArK ... k?e=w25vpM

[Lowlander]

Could it be doing a background process like auto-analyzing volume? Here while playing it hovers around 1%.

[PoorBoy2001]

I had "Level Playback Volume" checked. Unchecking doesn't seem to make any difference.

[Lowlander]

That's not it, there is an option to analyze volume for unanalyzed files. Key, is to make sure no background process is set to run that may explain this.

[PoorBoy2001]

I had that unchecked same as the wiki image.

Under Media Sharing MediaMonkey Server was enabled. I've unchecked it and MM seems calmer now. I'll give it a bit and see if the usage remains down.

[PoorBoy2001]

That calmed it for a bit, but back up and spinning at 24%CPU now.

[MeinOli]

Hey PoorBoy2001,

Thanks for flagging this issue. I have same the frustration with the CPU hogging – not cool! Let's dive into this:

OS: What's your OS and version? Windows, Mac, or Linux? Any recent updates?

MM5 Version: Which specific MM5 version are you rocking?

Plugins: Apart from OneDrive, any other plugins in the mix? List 'em if there are.

Background Check: Cool that there's no syncing/tagging drama. But have you peeked into Event Viewer for any oddities during those CPU spikes?

Machine Specs: What's under the hood? CPU model, RAM, and how much storage do you have left?

Got a hunch we can crack this together. Appreciate the patience!

Cheers

[Peke]

Hi,
MeinOli is right we should get the crack on this.

Media Server can point that some device on your network scans MM library, NAS, TV, AV receiver, Media Player, ... Alexa, Google home, ....

We would be interested in compressed Debug log as described here https://www.mediamonkey.com/forum/viewt ... 30&t=86643 and sent to us in support Ticket.

[PoorBoy2001]

Thanks for engaging and helping with this. Glad it's not just me seeing the issue

OS: What's your OS and version? Windows, Mac, or Linux? Any recent updates?
Window 11 Home v.10.0.22635 Build 22635 - on the preview plan so it generally does security updates and the like every few days.

MM5 Version: Which specific MM5 version are you rocking?
MM 5.1.0.2832

Plugins: Apart from OneDrive, any other plugins in the mix? List 'em if there are.
About 30 addons are in the list under Tools/Addons. I should clean these out - is there a link to instructions for removing them?

Background Check: Cool that there's no syncing/tagging drama. But have you peeked into Event Viewer for any oddities during those CPU spikes?
I'll keep checking as it occurs and post anything unusual.

Machine Specs: What's under the hood? CPU model, RAM, and how much storage do you have left? MSI GF65 Intel i7-10750H CPU @ 2.60GHz, 2592 Mhz, 6 Core(s).
BIOS AMI E16W2IMS.103, 2021-01-08
16 GB RAM
Drive C: 450GB/333GB free
Drive D: 930 GB/500GB free

[PoorBoy2001]

Ticket started with debug log sent.

In this case high cpu seemed to coincide with MM updating podcasts.

[Peke]

Hi,
That explains a bit as MM is downloading accessing and managing podcasts.

Please keep an eye on it and report back.

[PoorBoy2001]

It seems like once it gets to the high CPU state it persists indefinitely until I exit MM - even if it's hours later.

[Peke]

Hi,
This looks like Resource leak.
How often it happens? As if you can fetch full debug log it could help us find it.

[Peke]

Hi,
Dev, assigned for analyze. THX.

[PoorBoy2001]

Hi,
This looks like Resource leak.
How often it happens? As if you can fetch full debug log it could help us find it.

It happens every time MM is running on my machine.

By full debug log, do you mean from startup of MM until the issue occurs (and then a few minutes after?).