Firefox 3.0
Record number of downloads
2,950,109 downloads in USA as of 8:34 pm eastern (Wed. June 18th)
9,533,377 downloads worldwide.
They were hoping for at least 1 million.
I thing they were under-rating their software
and the people who want the newest version.
----- Original Message -----
From: "Pat McBride" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, June 18, 2008 6:20 PM
Subject: RE: [social] Download Firefox 3.0 Today
HELP!!!!!!!!!!!!!!!!! How do I change the colours on Firefox
3.0??????????/
Some of them are yellow, and can't be read. ANYBODY, please
help!!!!!!!!!!!!!! Otherwise, I'm going back to Microsoft!!!!!!!!!!!!!!!.
Pat
-----Original Message-----
From: Daniel Carrera [mailto:[EMAIL PROTECTED]
Sent: 2008/06/17 22:55
To: [email protected]
Subject: Re: [social] Download Firefox 3.0 Today
Rod Engelsman wrote:
Done. Very nice. Seems to load pages significantly faster... and here I
thought the bottleneck was my Internet connection.
One thing I love about FF3 is that they have really improved the memory
problems. They fixed 400 bugs/issues related to memory, including many
memory leaks. They also changed Gecko to use memory more efficiently.
Let me give some examples:
* Every item in the cache now has a timestamp and as they expire they
are removed from memory.
* They no longer keep a copy of uncompressed images in memory.
* They switched to a new memory allocator written by a FreeBSD guy. You
know how hard drives can get fragmented over time, right? Well, memory
gets fragmented too. You don't notice because you normally run an
application for only a few hours and when you close it, all the memory
it was using gets returned. But for an application like Firefox, which
could be running for several weeks at a time, memory fragmentation does
matter. I close my FireFox 2 about once every 3 weeks. That's when
memory consumption gets big enough that I get tired and close it. The
new memory allocator largely avoids fragmentation.
* One source of memory leaks was not Firefox itself, but the plugins.
The plugins have access to Firefox internals and they could create
circular object references where object A has a pointer to object B but
object B has a pointer to object A. No other part of the program is
using either A or B but they don't get removed from memory because Gecko
thinks that they are still in use. Hence, you get a memory leak. Gecko
1.9 has something in it that detects most circular references, even when
they are due to interaction with a plugin, and clears the memory.
Anyways, I'm very happy about the changes. My #1 issue with Firefox has
always been memory consumption. There are other nice new features, but
memory is my favourite feature.
Cheers,
Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
No virus found in this incoming message.
Checked by AVG.
Version: 8.0.100 / Virus Database: 270.4.0/1507 - Release Date: 08/06/18
07:09
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG.
Version: 8.0.100 / Virus Database: 270.4.0/1507 - Release Date: 6/18/2008
7:09 AM
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
