Bug 301349

==16848== 13,949,308 (2,404,864 direct, 11,544,444 indirect) bytes in 9,394 blocks are definitely lost in loss record 4,151 of 4,151
==16848==    at 0x4C2B1C7: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==16848==    by 0x28AC4152: MagnatuneXmlParser::parseTrack(QDomElement const&) (MagnatuneXmlParser.cpp:324)

The new in question:
> MagnatuneTrack * pCurrentTrack = new MagnatuneTrack( QString() );
subsequently added to a list
> m_currentAlbumTracksList.append( pCurrentTrack );
but never deleted it seems.

A strategically placed qDeleteAll in the dtor should take care of that.

Reproducible: Always

Steps to Reproduce:
1. wipe magnatune settings from amarokrc (update timestamp will prevent a rescan)
2. trigger a scan - e.g. disable and enable the store plugin
3. disable plugin once memory started growing
Actual Results:  
memory of MangatuneTracks not recovered

Expected Results:  
memory recovered

general note of interest: for validation purposes you might want to add debug statements to the ctor && dtor of the track class as memory usage alone will not paint an accurate picture. this is in particular because at least my Qt version has a leak in domdocument itself....