mixxx performance trouble on macOS is back

Bug #1920646 reported by Foss-4
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
New
Low
Unassigned

Bug Description

macOS 11.2.3

Todays 2.3 build (Mixxx-2.3-r8101-672fea11b2.dmg 2021-03-20 16:04) is responding very laggy (see screencast showing interaction with a dropdown in preferences).

While this may feel like going in circles I think this is a new problem and not identical to previous performace problems on macOS.

Spin Dump (1 year): https://bin.disroot.org/?12ae71af589da19b#9Zz6cqqadoRmqjKKRJ5vMxYhGniwRnbw3kfBFGjSYMiL

Process Sample (1 year): https://bin.disroot.org/?23e452609f3d8624#AEHu7xZbGbXYFopoX3PrF75MeJz7zvyccpKwBXKCMmgm

What is very strange, after letting mixxx sit for a bit, things normalise and the preference dropdown can be used as expected.

When the UI is "stuck" like shown in the screencast also scrolling in library is very laggy. This also returns to normal after a while.

Revision history for this message
Foss-4 (foss-4) wrote :
Foss-4 (foss-4)
description: updated
Changed in mixxx:
milestone: none → 2.3.0
importance: Undecided → High
Revision history for this message
Foss-4 (foss-4) wrote :

Well something is off. Mixxx goes to 100% CPU (hello again) and is not usable. Also the controller is not doing anything. A restart does not change this.

description: updated
Revision history for this message
Foss-4 (foss-4) wrote :

Now I have mixxx siting idle at 100% CPU and controller doing its thing. Not sure how to get a better understanding of this situation. Seems very volatile and having a hard time coming up with proper reproduce steps or consistency of the misbehavior.

Revision history for this message
ronso0 (ronso0) wrote :

can you somehow verify that there is only ONE Mixxx instance running?
like in some process explorer, there should only be one mixxx root process with N child processes.

I remember I saw something similar on ubuntu lately (mixxx @100% CPU) but it was due to accidentally starting mixxx twice and not properly killing the first process properly so it was appearantly blocking the second instance in some way.

Revision history for this message
Be (be.ing) wrote :

I cannot reproduce this on a 2017 iMac with a 5k screen, 3.5 GHz quad core Intel Core i5, 32 GB RAM, AMD Radeon Pro 575 4GB video RAM.

Revision history for this message
Be (be.ing) wrote :

That iMac is running macOS 11.2.3.

Revision history for this message
Be (be.ing) wrote :

and the CPU is an Intel Core i5 7600

Revision history for this message
Foss-4 (foss-4) wrote :

on macOS activity manager you see all running processes. Searching for "mixxx" brings up a single process and if you stick to UI from what I know it is not possible to launch the same app twice.

This is a 2017 MacBook Pro, 3,1 GHz Quad-Core Intel Core i7, 16 GB RAM, Radeon Pro 560 4 GB.

I am unable to reproduce the problem. I also talked to Ben and he was unable to reproduce. So the good news is, the problem is local and limited to my setup so this is not a 2.3 blocker. Lowering priority. I will keep an eye on this. IF you have more ideas what to do when this re-occurs let me know.

Changed in mixxx:
importance: High → Low
Revision history for this message
jus (jus) wrote :

Check that your cover-art columns in the library are not too wide eventually. I found that alone can bring the CPU utilization easily to 100% on idle.
See lp:1916880

Revision history for this message
Foss-4 (foss-4) wrote :
Revision history for this message
Foss-4 (foss-4) wrote :

have set it to square (which I think also would be the best default as otherwise the covers are cut-off)

Changed in mixxx:
milestone: 2.3.0 → none
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/10363

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.