kmself@ix.netcom.com wrote:
> I've been kicking this issue around for a while and would be interested
> in ideas for a low-memory monitor or something similar which would
> identify high-utilization processes and kill them rather than bringing
> the entire system to a crashing halt.
>
> Then ther
on Tue, Nov 28, 2000 at 03:39:42PM -0500, Harry Henry Gebel ([EMAIL PROTECTED])
wrote:
> On Tue, Nov 28, 2000 at 12:03:12PM -0800, kmself@ix.netcom.com wrote:
> > on Tue, Nov 28, 2000 at 07:20:53AM -0800, Greg Strockbine ([EMAIL
> > PROTECTED]) wrote:
> > > My system totally froze up, apparently
On Tue, Nov 28, 2000 at 12:03:12PM -0800, kmself@ix.netcom.com wrote:
> on Tue, Nov 28, 2000 at 07:20:53AM -0800, Greg Strockbine ([EMAIL PROTECTED])
> wrote:
> > My system totally froze up, apparently to memory exhaustion? Can this
> > be?
>
> Similarly, 256 MB, recently upgraded from 96 MB. F
on Tue, Nov 28, 2000 at 07:20:53AM -0800, Greg Strockbine ([EMAIL PROTECTED])
wrote:
> boy I can't believe this.
> My system totally froze up, apparently to memory exhaustion? Can this
> be?
Yes.
> Debian potato, gnome desktop, 256 Mbytes of memory.
Similarly, 256 MB, recently upgraded from 96
Can't actually answer your question :) but with reference to the
last bit,
>why does Mozilla have such a huge foot print?
>It takes up around 100 Mbytes while Netscape is
>down around 15 Mbytes.
It doesn't actually. That's the same smaller chunk of memory
boy I can't believe this.
My system totally froze up, apparently to
memory exhaustion? Can this be?
Debian potato, gnome desktop, 256 Mbytes
of memory.
gkrellm, the system monitor, was froze too,
but the display showed the swap file was
down to 0 bytes free. There was about 23 Mbytes
of main me
6 matches
Mail list logo
