50% CPU usage at launch, 100% 7 seconds later.

[mixxxbot]

Reported by: tfwnogf
Date: 2021-09-11T11:47:06Z
Status: Fix Released
Importance: High
Launchpad Issue: lp1943320
Attachments: mixxx.log

---

Mixxx version: Mixxx 2.3.0 (git 2.3.0 (HEAD); built on: Jun 28 2021 @ 20:44:54; flags: -pipe;-O3;-ffast-math;-funroll-loops;-fomit-frame-pointer;-mtune=generic;-Wall;-Wextra;-Woverloaded-virtual;-Wfloat-conversion;-Werror=return-type)

OS: Linux Mint 20

I encountered this yesterday but quickly found a fix (removing the config file). This bug has not happened since.

I've never manually edited the config file, all the settings were set from Mixxx's GUI.

Description of the bug: Mixxx will be at 50% CPU usage at launch (orange in the CPU load), then it will go red and take 100% few seconds later. No music could be played when this happend.

Fyi, Mixxx never reached the orange CPU load before on my computer, even when playing 4 decks with lots of FX.

Is it possible the config file was somehow corrupted, or it's a combination of settings that caused this crash?

I attached the logfile, if you want to have a look at my configfile: https://pastebin.com/eQ4maRjM
The password to read it is snQSG2ivju

As a note, this bug is 100% reproducible for me when I replace my configfile with this old one.

[mixxxbot]

Commented by: tfwnogf
Date: 2021-09-11T11:47:06Z
Attachments: mixxx.log

[mixxxbot]

Commented by: daschuer
Date: 2021-09-12T22:18:36Z

---

I can confirm this with Ubuntu Groovy when copying the insane internal clock bpm from your cfg file.

[InternalClock]
bpm 1.36194e+13

I will have a look why this can happen and affects the CPU load that badly.

[mixxxbot]

Commented by: Be-ing
Date: 2021-09-12T22:33:27Z

---

Why is [InternalClock], bpm even stored in the config file?

[mixxxbot]

Commented by: daschuer
Date: 2021-09-19T22:07:17Z

---

#4312

[mixxxbot]

Issue closed with status Fix Released.