| 2016-11-12 22:53:22 |
Be |
bug |
|
|
added bug |
| 2016-11-12 22:54:07 |
Be |
description |
When a deck has a track loaded to it for the first time since opening Mixxx, CPU usage spikes. This can cause an xrun when loading the second track to be played in a set. This occurs with tracks that are already analyzed, so it is not an issue of analyses being run. I think whatever initialization is done on first track load should be done as Mixxx is starting. |
When a deck has a track loaded to it for the first time since opening Mixxx, CPU usage spikes. This can cause an xrun when loading the second track to be played in a set. It does not occur when loading subsequent tracks to the deck. This occurs with tracks that are already analyzed, so it is not an issue of analyses being run. I think whatever initialization is done on first track load should be done as Mixxx is starting. |
|
| 2016-12-06 21:44:54 |
ronso0 |
bug |
|
|
added subscriber Ronny Sandig |
| 2017-01-11 20:16:52 |
Daniel Schürmann |
mixxx: importance |
Undecided |
High |
|
| 2017-01-11 20:16:54 |
Daniel Schürmann |
mixxx: assignee |
|
Daniel Schürmann (daschuer) |
|
| 2017-01-11 20:17:00 |
Daniel Schürmann |
mixxx: status |
New |
In Progress |
|
| 2018-02-07 08:35:37 |
Be |
summary |
spike in CPU usage when loading track to a deck for first time |
spike in CPU usage when loading track to a deck |
|
| 2018-06-09 16:25:15 |
Be |
summary |
spike in CPU usage when loading track to a deck |
priority inversion in the engine |
|
| 2022-10-08 20:37:52 |
Swiftb0y |
bug watch added |
|
https://github.com/mixxxdj/mixxx/issues/8688 |
|
| 2022-10-08 20:37:54 |
Swiftb0y |
lock status |
Unlocked |
Comment-only |
|
