{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Ryan La Riviere <[EMAIL PROTECTED]>
On 03/05/2002 00:56, "Kim Slawson" <[EMAIL PROTECTED]> wrote:
>
> output from top:
>
> ... after starting fire
> PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE
> 7151 Fire 5.5% 2:31.78 6 137 685 62.8M 37.0M 73.1M 176M
> ... some time later
> 7151 Fire 6.7% 12:58.84 7 140 898 73.4M- 45.7M 86.8M- 200M+
> ... and still later
> 7151 Fire 11.0% 23:27.39 7 140 1243 92.4M+ 71.7M+114M+ 255M+
Hmmm...I'm seeing the same thing. I'm running the 3/1 build so it's
something that's been there a little while.
My top output:
PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE
3001 Fire 0.0% 43:41.67 5 133 2054 124M 159M 140M 432M
Fortunately, mine has been fairly light on CPU usage when idle. It will
surge to 14% and then back to 0%. The RAM usage does slowly grow. Of
course with Entourage eating a lot of CPU, Fire may not be getting as much
of a chance. :) But Entourage is using FAR less RAM than Fire. Very odd.
I could send someone a sample of Fire while it's eating up RAM.
That's my story and I'm sticking to it.
--
Ryan "My hometown is nowhere, my friends are everywhere." La Riviere
System Administrator; Drexel University
215.895.6010
<http://staff.tdec.drexel.edu/~edljedi/>
{#} ----------------------------------------------------+[ fire ]+---
