Slashdot Mirror
Firefox 3 Beta 1 Review
DaMan writes "The newly-released Firefox 3 beta 1 has been reviewed by ZDnet and the verdict is that it is good. 'Is Firefox 3.0 going to be better? Given what I'm seeing so far, I think so. Why? Because it looks like Mozilla have gone back to basics and worked on what really matters to users — security, speed and ease of use ... Everything about Firefox 3.0 beta 1 is fast. The download package is small which means that it comes in fast, the installation is fast, the browser fires up fast, pages and tabs open fast, the browser shuts down fast, and the uninstall process is fast and painless.'"
Instead of this windows-screenshot-centric review, what geeks like me really want are the release notes.
But... Firefox is already a lightweight derivative... of Mozilla Suite (SeaMonkey)...
It's lightweight in that it has less compiled code in it, alas it makes up for it with an excessive amount of scripted code.
What flamewar? For nearly two years, Mozilla developers have asked users to file good memory leak bug reports and have even supplied tools for doing so. If you're still having problems, simply report them and they can be fixed. You can report any bugs in Firefox 3 beta directly to Bugzilla, or discuss them in the MozillaZine Firefox Builds forum first.
What a fool believes, he sees, no wise man has the power to reason away.
But those leaks are up to the affected extension authors to fix.
Beware: In C++, your friends can see your privates!
Yes, many users were mistaking fragmentation (and caching) for memory leaks. We've been making this exact statement for years in the MozillaZine forums. But there are actual memory leaks, also. You can't point the finger at any one cause. At any point in time, Firefox memory use is some combination of memory needed to display the open pages, various caches (not just the two people talk about all the time), fragmentation, and possibly memory leaks. The only news is that the developers are getting diminishing returns on fixing leaks, and are now turning to reducing fragmentation to reduce normal memory use.
What a fool believes, he sees, no wise man has the power to reason away.
I run FF 24/7 for weeks on end on Windows and it never goes over 200MB. I accept it's still a lot but then I also tend to browse lots of forums with crappy animated avatars and the like. I can have 20 tabs open across three windows and it still doesn't go over 200. I'm amazed that some people find it using memory in the order of gigabytes.
See pavlov.net blog on Memory fragmentation in firefox.
I ran in to this problem back in the days where 4MB of memory was a lot. My program needed a lot of large objects with a short persistence. The upshot of this was that the program soon ground to a halt due to swapping memory I partially overcame the problem by writing my own allocation algorithm which kept separate lists of blocks of different sizes, hence it managed to recycle much of the memory blocks.
There are four sorts of people in the world: fools, lunatics, idiots and morons. - Umberto Eco, Foucaut's pendulum.
Maybe they need to realize when some pages that people make are taking up too much memory, or some extensions are using too much memory. If you go to a page that adds a couple new elements to the DOM every 3 seconds, and leave it on all night, you're going to end up with your browser consuming gigabytes of RAM. If you have a plugin which doesn't release it's memory, and keeps on asking for more, you're going to have a browser that takes up 2 GB of RAM. If you try to open up a huge XML file with your browser, then you're going to have a problem with the browser taking up lots of memory. Those are the only times I've ever seen my usage go above 200 MB. Under normal browsing conditions, even leaving Firefox open for weeks, I've never seen it go over 200 MB. When it does, it's because some rogue page keeps adding stuff to the DOM.
Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
Just last week I went to move 40,000+ small (less than 700 byte) files off an FTP server. I was lazy and decided to just use IE6's built in FTP client. I was moving the files in the background and doing other "work" in Firefox while it moved the files. A few hours later everything on my PC started closing out (crashing), even Explorer and I was left with Firefox and a few other applications running. IE, Explorer, Visual Studio 2005, and a few other applications just aborted when my machine ran out of memory (1G RAM, 2G swap).
Why IE was using over 2G of RAM for moving 40,000 files I have no clue, but I was impressed that Firefox continued to run when even Windows Explorer (and even Visual Studio... Microsoft's "crowning achievement") shut down. I guess Microsoft doesn't plan on running out of memory when coding applications.
Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
It seems Firefox 3 also passes the Acid2 test.
A few other minor observations - it won't install any add-ons unless they update securely. So far the only add-ons I've been able to install successfully are GMail Notifier and Adblock Plus. I'm not complaining (since it is a beta release specifically for developers and testers). I just can't wait for development and support of my favorite add-ons to take place!
One nice thing I noticed is that if you are installing add-ons from a site that is not in the exceptions list you can just accept it via the title bar now instead of having to open the settings, add the site, reload it, and wait again.
So far I'm impressed! It's fast and smart.
"This food is problematic."
So, you've filed a report for this -- right?
They have a lightweight version,it is called Kmeleon. That said,I do hope they fix the memory problem in FF. While I like Kmeleon,I do miss my extensions(although they have added adblock support,which was my main extension)
ACs don't waste your time replying, your posts are never seen by me.