On 19 Sep, Chris Kuklewicz wrote:
> 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
On 19 Sep, 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 tr
mary 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 mu
ny plan to add
> a search feature? If not, then I could design and implement it.
As always, any coding of useful features will be happily accepted ;). I
don't believe such a feature was planned in the immediate future, so you
won't be replicating anyone elses work with that.
> I no
does this with xmms. ( see xmms-gtk-playlist at
http://web.mit.edu/chrisk/www/index.html ). Is there any plan to add
a search feature? If not, then I could design and implement it.
-
I noticed the memory footprint was about 27MB (which includes shared
libs). The footprint of xmms with the sam
I'm sure elrod will send out an announcement soon, but Karl would probably
be happy to know Freeamp 2.0.6 is released. I haven't tested yet.
On Sat, 25 Mar 2000, Mark B. Elrod wrote:
> Due to some stuff I needed to do on win32 I pushed the date to monday.
> Sorry ...
>
> elrod
>
_
Due to some stuff I needed to do on win32 I pushed the date to monday.
Sorry ...
elrod
Karl Ove Hufthammer wrote:
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, March 21, 2000 2:24 PM
> Subject: Re: freeamp'
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 21, 2000 2:24 PM
Subject: Re: freeamp's memory footprint?
> There is a bug in 2.0.3 - 2.0.5 that will chew up a bunch of memory
> when FreeAmp switches tracks. We're g
pert at understanding
> all the figures. How large should the memory footprint be?
>
> Mem: 127884K av, 124780K used, 3104K free, 27856K shrd, 2620K buff
> Swap: 361420K av, 56452K used, 304968K free 18324K cached
>
> PID USER PRI NI SIZE RSS SHA
my environment:
Red Hat 6.1 w/ latest updates
P3-450/128 w/ on-board Crystal 4232 chipset
I'm seeing freeamp chew up a lot of memory.. here are some lines from top
(during mp3 playback); although frankly I'm not an expert at understanding
all the figures. How large should the memory
10 matches
Mail list logo
