high memory consumption when indexing library
Bug #801700 reported by
ocknoz
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
Medium
|
Daniel Schürmann | ||
1.11 |
Fix Released
|
Medium
|
Daniel Schürmann |
Bug Description
When launching Mixx for the first time after installation I let it import my music library. During the import process Mixx continued to use up more and more memory (almost 4gb).
It didn't release any memory, even after importing was done.
When the import was finished I restarted Mixx and it used only 120mb.
Mixx 1.9.0 x64
Library: 34,500 tracks, 200gb.
System: Win7 64bit, i7 950 3GHz, 12gb RAM (see also attached DxDiag.txt)
Memory consumption: http://
Changed in mixxx: | |
status: | New → Confirmed |
Changed in mixxx: | |
assignee: | nobody → Daniel Schürmann (daschuer) |
Changed in mixxx: | |
importance: | Undecided → Medium |
tags: | added: library memory performance |
tags: | added: scanner |
Changed in mixxx: | |
milestone: | none → 1.11.0 |
Changed in mixxx: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The bug has something to do with the patch from Bug #604018
The library scanner collects all tracks in ram and commits them to the database at one.
The scanner itself releases the memory after commit. Bud there is also a track cache, maybe this still has the memory.
My valgrind analysis seems not to report a report a memory leak from this issue.
I think it is a good idea to limit the memory usage of the library scanner.
How does the track cache work? Is there also a memory limit?