Comment 8 for bug 410841

Of course, holding TrackInfoObjects has advantages. The key of every DJ software, however, is stability. Moreover, a DJ system must be designed to meet the requirements of non-stop playing (in Germany a club session starts at 10p.m and ends at around 5a.m). There is no way out to tackle this problem.

To my mind, there are two possibilities to overcome this problem:
1. Follow the suggestion from Robin Sheat and introduce a cache...
2. It might be possible to serialise TrackInfoObjects in the XML file, Mixxx uses to store the library.

RJ Ryan wrote:
> The main problem with the growing memory usage is that TrackInfoObjects
> (especially the waveform generated for the TIO) are not free'd after
> some interval of not being in use. This means that if you load 10
> tracks, the memory to store the waveform for each track is resident in
> memory. This is nice because if you reload the track, the waveform shows
> up instantly -- but it's not nice because if you are on a system with
> low ram, or DJing for long periods of time, you'll run out of memory :-/.