OW using WAY too much RAM

[Ken Case]

The spinning disc cursor is due to a deadlock (perhaps the one between 
JavaScript and cookies which we already know about and are working on 
fixing, but perhaps one we don't know about), not memory use.

VSIZE is how much memory we have defined, but it doesn't actually 
indicate how much memory we're using.  (It's mostly zero-filled unmapped 
unused regions.)  The RSIZE number indicates the amount of real pages 
which is allocated, but in this case most of that (170MB) are shared 
with other processes (i.e., they're mostly read-only maps of shared 
libraries, plug-ins, etc.).

The number which measures private memory allocated by OmniWeb is RPRVT, 
and with in active use with 7 browser windows open 113MB isn't 
unreasonable.  If you flush your cache (or wait five minutes for things 
in the RAM cache to expire), it may drop more, and as you close windows 
you should see it continue to drop with each one.

Hope this explanation helps!

				Ken

On Friday, January 4, 2002, at 09:24 AM, Jake Robb wrote:

> Okay, I'm downloading 4.1sp24 right now... I'll let everyone know if 
> this
> remains a problem.
>
> OW 4.1b1 right now is stuck on a spinning disc cursor.  My first 
> explanation
> for this is described by this line from top:
>
> COMMAND    %CPU  TIME   #TH #PRTS #MREGS RPRVT  RSHRD  RSIZE  VSIZE
> OmniWeb      0.6%  1:42:05  49   424  2435   113M   170M   260M   533M
>
> I've got 768MB of RAM.  Those numbers seem like they've gotten a bit 
> high,
> especially considering that I only have seven browser windows open (one
> loading a page, one I was entering text into a text field, five 
> completely
> idle).
>
> Let me know what I can do to help investigate this.
>
> -Jake
>
> _______________________________________________
> OmniWeb-l mailing list
> OmniWeb-l at omnigroup.com
> http://www.omnigroup.com/mailman/listinfo/omniweb-l
>