High CPU usage but only sometimes, suspected Auto-Playlist but don't know which

[SonicRings]

I'm on version 3.5.8143 P and "continuously monitor" is un-selected in the Library tab.

I've been experiencing this issue for a very long time now. Sometimes, MusicBee will start to use anywhere between 8-12% CPU (I have a Ryzen 5800X so that's a considerable amount of usage for this CPU) which pretty much tanks single core performance, causing many games to run up to 50fps lower (I game at 120fps).

I often get this issue to happen after actually interacting MusicBee. Whether it's scrolling through playlists or my library. It only stops when I close and reopen MusicBee.

I have no idea what causes it as I can't consistently reproduce the issue.

I suspect that an autoplaylist is causing this issue. However, I don't know which one is the culprit. I have quite a few.

What should I be looking out for in an autoplaylist's settings to be able to determine whether it is the cause? Is there some sort of MusicBee task manager that can tell me what it's doing at any given time?

[phred]

I think you should update to the latest 3.6 and see if you still have the same issue. The version you're using is more than two years old.

Why do you suspect an auto-playlist is causing it?
I can't think of a reason why a playlist could be a cause. After all, a playlist (auto or static) is nothing more than a text file.

[SonicRings]

I think you should update to the latest 3.6 and see if you still have the same issue. The version you're using is more than two years old.

Why do you suspect an auto-playlist is causing it?
I can't think of a reason why a playlist could be a cause. After all, a playlist (auto or static) is nothing more than a text file.

I can't use 3.6 as it has completely broken the way hotkeys work last tried. https://getmusicbee.com/forum/index.php?topic=42394.msg231549

I thought it was an auto playlist trying to refresh based on criteria. Other than that, I don't know what could be the issue. What do you suspect?

[Steven]

The media key behaviour was reverted recently in the v3.6 patch version.
Try disabling any plugins you might have enabled

[phred]

What do you suspect?

I suspect the fact  that you're using a version of MB that's more than two years old.
And/or it could be a plugin as Steven suggests.

Which plugins do you have installed and enabled?

Update to the latest 3.6 patch and test. If you still have the problem, disable all your plugins and restart MB. Enable one plugin and test. If it works, enable the next plugin and test. Until you find the one that's causing the issue.

[SonicRings]

That's good to hear that 3.6's hotkey issue has been fixed!

I just now figured out what causes the high CPU usage on my end. It's whenever I queue a song. The moment I queue a song, my CPU jumps to 10%+ and stays there indefinitely until I restart MusicBee.

As for my plugins, I currently have these enabled:

last.fm
cd art display
additional tagging tools
discordbee
last.fm playlist generator
last.fm recommendations
last.fm statistics
love me, love me not
lyrics reloaded
mb_clipboard-search
mb_songhistory
minilyrics for musicbee
musicbee nevers sleeps
playlist history
scrobble short tracks
scrobblerbrainz
theater mode

Are any of the plugins I listed known to cause this issue I'm getting? I'd like to rule those out before I go through with updating.

[SonicRings]

I've just updated to 3.6.9245 P and am still getting the same issue. On top of that, it now takes almost a minute for MusicBee to close regardless of queue size. I've gone back to the version I was on previously and am curious what else I can check to solve this issue.

While testing, I tried clearing my queue and restarting MusicBee. Upon restarting, queuing files no longer caused the high CPU issue I was getting. This happened on both 3.6 and 3.5.

My queue has 100k songs. I'm curious why MusicBee can operate normally with a queue this large, but the moment I queue a song, it gets stuck using 8-12% CPU indefinitely until I restart? I'd understand if it would always be stuck at a high CPU usage due to the queue being too large, but this only occurs when a new song is added to it, so I'm curious why that may be the case, and if there's anything I can do to circumvent this?

I will test to see at what queue size this issue occurs when I have more time, but I like seeing how many tracks I have listened to on each of my MusicBee installs on a per-system basis which is why I choose to keep my queues long. I understand I can just make a playlist to dump the queue to whenever it gets too long, but I really enjoy seeing the number go up as I listen. Some insight would be greatly appreciated.

[Steven]

instructions have already been provided so i am locking this topic

see https://getmusicbee.com/forum/index.php?topic=29381.msg235236#msg235236