Track objects should be unique per loc
Bug #409591 reported by
reacocard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Exaile |
Fix Released
|
High
|
reacocard |
Bug Description
Title says it all. We should ensure that there is exactly one Track object generated for every loc. This is probably most easily done by overriding the construction of Track objects themselves, either by turning Track() into a factory function, or by giving the class a __new__ method that returns the existing instance if there is one. This avoids potential memory leaks and ensures we dont get two desynced copies of a track's metadata.
Changed in exaile: | |
importance: | Medium → High |
Changed in exaile: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
fixed in trunk