On Sun, Jan 2, 2011 at 5:32 PM, Landry Breuil wrote:
> On Sun, Jan 02, 2011 at 05:05:29PM +0100, Landry Breuil wrote:
>> On Sun, Jan 02, 2011 at 10:44:01AM -0500, Ted Unangst wrote:
>> > First, see http://kb.mozillazine.org/Browser.cache.memory.capacity
>> >
>> > Next, check about:cache to see tha
I wonder if this is what makes firefox so TERRIBLY slow for js-heavy
sites...
/Alexander
On 01/02/11 16:44, Ted Unangst wrote:
> First, see http://kb.mozillazine.org/Browser.cache.memory.capacity
>
> Next, check about:cache to see that firefox is using 2048K, the default
> size for 32MB of RAM.
On Sun, Jan 02, 2011 at 05:05:29PM +0100, Landry Breuil wrote:
> On Sun, Jan 02, 2011 at 10:44:01AM -0500, Ted Unangst wrote:
> > First, see http://kb.mozillazine.org/Browser.cache.memory.capacity
> >
> > Next, check about:cache to see that firefox is using 2048K, the default
> > size for 32MB of
On Sun, Jan 02, 2011 at 10:44:01AM -0500, Ted Unangst wrote:
> First, see http://kb.mozillazine.org/Browser.cache.memory.capacity
>
> Next, check about:cache to see that firefox is using 2048K, the default
> size for 32MB of RAM.
>
> I haven't dug into the source, but somewhere, firefox is faili
First, see http://kb.mozillazine.org/Browser.cache.memory.capacity
Next, check about:cache to see that firefox is using 2048K, the default
size for 32MB of RAM.
I haven't dug into the source, but somewhere, firefox is failing to detect
the amount of RAM I have. This is a simple sysctl call to
