Open the music browser, play a few tunes, then select each Theme and return to the Freeamp theme. The theme memory is NOT released: PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND 21310 ckuklewi 0 0 41260 38M 3528 S 0 0.0 50.4 0:05 freeamp 21311 ckuklewi 0 0 41260 38M 3528 S 0 0.0 50.4 0:00 freeamp 21312 ckuklewi 0 0 41260 38M 3528 S 0 0.0 50.4 0:00 freeamp 21313 ckuklewi 0 0 41260 38M 3528 S 0 0.0 50.4 0:00 freeamp 21314 ckuklewi 1 0 41260 38M 3528 S 0 2.8 50.4 0:02 freeamp 21315 ckuklewi 0 0 41260 38M 3528 S 0 0.0 50.4 0:00 freeamp 21320 ckuklewi 0 0 41260 38M 3528 S 0 1.1 50.4 0:21 freeamp On Tue, Sep 19, 2000 at 04:55:05AM -0400, Sean Ward wrote: > > Yep, freeamp as a whole is a lot more bloated than say, winamp or XMMS. The > primary size difference comes from the musicbrowser, because it loads all > the metadata entries at startup, so has a memory footprint proportional to > the number of tracks in your collection. Additionally, there are a bit too > many internal copies which go on, which are part of the general musicbrowser > issue ;). In essence, updating this system is one of the top priorities for > the next FreeAmp rev (outside of the 2.1 beta series) since it requires a > fairly significant rewrite to the entire musiccatalog and browser code. In > the interim, just consider the fact that freeamp will load all the metadata > for a playlist faster than XMMS, and can recommend playlists for ya, so you > get something extra for the memory usage ;) > > -Sean > > As always, Rob or Isaac please correct me if I'm in error, especially about > error handling ;) > > _______________________________________________ > [EMAIL PROTECTED] > http://www.freeamp.org/mailman/listinfo/freeamp-dev _______________________________________________ [EMAIL PROTECTED] http://www.freeamp.org/mailman/listinfo/freeamp-dev
