{#}  Replies are directed back to [EMAIL PROTECTED]
{#}  To reply to the author, write to Ernest <[EMAIL PROTECTED]>

This didn't used to be a problem for me, but as of late I have been having
the same issue.



On 3/4/02 9:56 PM, "Kim Slawson" <[EMAIL PROTECTED]> wrote:

> {#}  Replies are directed back to [EMAIL PROTECTED]
> {#}  To reply to the author, write to Kim Slawson <[EMAIL PROTECTED]>
> 
> On Mon Mar 04 18:47:00, Eric Peyton wrote:
>> {#}  Replies are directed back to [EMAIL PROTECTED]
>> {#}  To reply to the author, write to Eric Peyton <[EMAIL PROTECTED]>
>> 
>> All,
>> 
>> We are rapidly approaching the next release of Fire.  If there are any
>> outstanding problems that you think this release cannot be released
>> without, please let me know ASAP.  Input from people running the most
>> recent CVS builds is especially welcome.
> 
> anyone, feel free to correct me if this has been adressed
> before, but I have a problem that after a period of time (from
> several hours to a day) Fire will consume all available memory.
> 
> it seems some component, or components, has a serious memory
> leak.  this is with both TOT and the daily builds, by the way.
> 
> it's serious because it eventually causes swap to become used,
> and on machines with little space for swapfiles, that can lead
> to corruption.  well, that and everybody hates memory leaks and
> sluggishness.  quitting and restarting fixes it, but it'd be
> nice not to have to do that, and sometimes (when the user is
> away for long periods of time) that's not possible.
> 
> 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+
> 
> 
> (this example is rather mild, over the period of about two
> hours, though normally it seems to eat memory faster)
> 
> the rate of memory usage increase (slope) does seem to
> correspond at least somewhat with activity.  though the rate of
> virtual memory usage increase seems to be somewhat linear,
> without as much dependance on user interaction.
> 
> watching top now I can see it growing, before my eyes.  :-/
> 
> 
> Kim Slawson                                      [EMAIL PROTECTED]
> Computer Science House                    http://www.csh.rit.edu
> Rochester Institute of Technology             http://www.rit.edu
> 
> ---------------- PGP key available upon request ----------------
> 
> 
> {#} ----------------------------------------------------+[ fire ]+---
> 
> 
> 
-- 
Ernest - [EMAIL PROTECTED]
    <http://www.macaddict4life.com>
*877MacTank: The only choice for all of your Macintosh technical support
needs.*
�The test of democracy is freedom of criticism.� -David Ben-Gurion
�Man�s capacity for justice makes the democracy possible; but man�s
inclination to injustice makes democracy necessary.� -Reinhold Niebuhr 


{#} ----------------------------------------------------+[ fire ]+---


Reply via email to