memory leak when changing skins
Bug #1459419 reported by
Daniel Schürmann
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Confirmed
|
High
|
Unassigned | ||
Bug Description
The used memory amount is growing by each skin change.
| Changed in mixxx: | |
| importance: | Undecided → High |
| milestone: | none → 1.12.0 |
Revision history for this message
| Max Linke (max-linke) wrote | #1 |
Revision history for this message
| Owen Williams (ywwg) wrote | #2 |
| Changed in mixxx: | |
| status: | New → Confirmed |
| Changed in mixxx: | |
| milestone: | 2.0.0 → none |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #3 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
I just started looking a little bit into this. It is kind of hard to get anything our of valgrind here since it crashes mixxx when I try to change the skin (with mixxx running in valgrind).
But from the information I get I can already see that there is a leak in creating and destroying the GLShaders. One can also test that by chosing a non GL waveform, changing the skin then increases the used memory by only a few MB instead of like 30-50MB.