High memory usage with large collections
Bug #372980 reported by
Mehdi Abaakouk
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Listen |
In Progress
|
High
|
Unassigned |
Bug Description
Hi,
after the first start, before adding any library, Listen was using ~85MB memory, playing one file, some plugins loaded.
Now I added my "Albums" folder as library, and after it finished scanning those few 28657 files, it was consuming ~390MB.
After exiting and restarting, it's consuming 456MB, and that is the constant level now.
Switching between "all artists" and an artist with only one file in the library browser makes a difference of ~4MB for displaying the list of tracks.
The songs.db has 31MB, 1 file in the playlist.
This ticket was migrated from the old trac: re #840
Originally reported by: thomask
Changed in listen: | |
milestone: | none → 0.7 |
Changed in listen: | |
status: | Confirmed → In Progress |
milestone: | 0.7 → 0.6.3 |
Changed in listen: | |
milestone: | 0.7 → none |
assignee: | Mehdi Abaakouk (sileht) → nobody |
To post a comment you must log in.
I can confirm that memory usage seems to increase linearly with music library size. I have about 9000 tracks in my library and listen hovers around 300-320Mb resident memory usage (as reported by top).
Originally reported by: paol