Tagger: High CPU Usage With M4A Fingerprint Calculation

(Okay, I admit that this title was a joke.)

Recently I noticed that my computer starts overheating for no reason. Sometimes, after a while the fan kicks in really hard and my computer gets really hot. When I say really it’s, like, it suddenly starts to get really noisy.

It happened again a few minutes ago, so I opened Mission Center, and I may have found the culprit 👀

Capture d’écran du 2023-08-17 15-34-18

I remember that I’ve opened Tagger briefly to edit some tracks, and closed it directly after using the shortcut ctrl + Q before continuing doing some things (using GNOME Builder, Edge and Workbench, along with other tiny apps like the Icon Library, Typography, etc.) When I took the screen, only Mission Center was opened though.

Now that I think about, I’m really unsure if the fan issue started since I use Tagger, or only since I use the last beta version 🤔 Edit : still unsure if it’s related to the beta version, but when I think about some times when it got really noisy, I think it was always when I used tagger, sometimes quite a lot.

I’m gonna do some tests to see. I didn’t saw any other issue about that, so maybe it’s just me or under really particular conditions 🤔.

But if it’s really Tagger, wow draining nearly 30% of the battery in about 20 minutes to edit some metadatas is really a lot lol. (it’s not even exagerated x))

Anyways, I’m still in vacations but I’m gonna post a reply if I have some other infos or precise steps to reproduce. If you have any request feel free to ask ! (I’m using Fedora Silverblue on a Microsoft Surface Laptop Go 2)

About this issue

  • Original URL
  • State: closed
  • Created 10 months ago
  • Comments: 30 (17 by maintainers)

Most upvoted comments

Good news tho!! @fsobolev found the fix to get the calculation of the file working on flathub version of the app too 😃

Oh wow, glad to hear this !

Ok fixed all the UI stuff…just waiting for an updated packaged of our backend and I’ll release a new version for you to try

One side note : if you plan on using Silverblue (I doubt but anyways) installing the surface kernel doesn’t seem to be easy. Like you can but it requires some workaround I think.

Yeah I just stick with fedora workstation 38 haha

I’ll also make it where all the fpcalc instances stop on close

I completely agree on that x)