Firefox Minefield Alpha

Just to be clear. These are just the Firefox nightly trunk builds that Mozilla has been providing for a long time. They contain bleeding edge code with the latest changes and are updated all the time. However, they can also contain nasty bugs. It's basically like running Safari with the latest Webkit.

Opera doesn't provide trunk builds, but they do provide snapshots of the current to-be-released branch. When the builds represent a major release, you get to test a lot of upcoming, bleeding edge changes. You can even find some experimental builds at http://labs.opera.com/

The main thing about Firefox trunk builds that might bug you is the extension support. Extensions often have to be updated (including the addons site) before you can install some of your favorite extensions. You can use the nightly tester tools to override the extension compatibility test, but even that doesn't work a lot.

Firefox latest trunk builds might also use your Firefox stable profile automatically and booger it up, so be careful. Load firefox.exe -p, create a profile named trunk. Then setup a shortcut that "loads firefox.exe -p trunk". You can also run two instances of Firefox (each using their own profile) if you set the environment variable MOZ_NO_REMOTE=1. You can also do it by passing "firefox.exe -no-remote -p trunk". (Just note that -no-remote might mess with Firefox launching Thunderbird)

With Safari, it's almost always a good idea to run the latest Webkit. It's usually stable and you get all the good fixes. Opera's snapshots are most of the time great too.
 
Have they fixed the bug where if you have a lot of FF tabs/windows open, Flash stops working? Y'know, the one where the video will load (in it's entirety most of the time), but you can't get it to keep playing as it stops every 3-4s (you can manually skip it ahead, but you have to do it every 3-4s). Rather annoying... Only happens when you've left those tabs/windows open for a while though. You could crash the browser, restore everything, and now Flash starts working again, bleh.
 
they would first need to fix their memory leak and usage problem. Yes it is still there in FF3. After opening 4 or so tabs, reading whatever, then closing them, FF3 still is taking 100MB of ram. WTF

It closes itself eventually, though not instantly... Doesn't take more than 20-30s though. It does get stuck when you've got a ton of stuff open and you close it all (whether properly or thru a crash), I've seen FF3 choke while trying to liberate 500MB+ of memory it's gobbled up. You can always do it manually of course, but meh.

FF3's memory usage is still better than FF2's or IE's... Chrome ends up using more memory AFAIK exactly because each tab is it's own process, so there's an upside and a downside either way. As long as FF remains stable I think I prefer their approach. I'm sure they can find a way to move tabs from one window to another w/o reloading 'em too (a-la-Chrome).
 
Firefox uses RAM for caching data, not the hard drive as IE does with the Temporary Internet Files folder. You set the amount of RAM available to the cache in the Options - Advanced - Network tab and that's that.

If you load up 4 tabs of content (each page has content, yanno) and that content gets cached into the RAM cache, even when you close those tabs the content remains cached in the RAM cache up to the limit of the cache. The default size iirc is 77MB, once that's fully populated it'll remain so and that RAM usage is on top of what Firefox requires for itself.

Whereas with IE those temporary files are stored on the hard drive, Firefox caches them in RAM so that's why opening, loading, and closing tabs still shows the so-called "excessive" RAM usage.

What you're seeing is perfectly normal operation for Firefox, I don't get why so many people bitch and gripe about it, geez. Learn how the damned browser functions and it's no longer an issue. Applied knowledge is power, yanno...

Using the RAM cache is part of what makes Firefox faster than IE these days, it's writing to and reading from RAM itself for using temp storage with webpage content. Some items like actual downloads will go into the Temp directory under your user profile depending on what they are (YouTube videos, Flash applets, etc) but the majority of it gets stuffed into the RAM cache.

All perfectly normal operation...
 
Wow, I was skeptical when I read about it, but it really is noticeably faster! The RAM hit is well worth it.

I wonder if IE would go this fast if the temp files were stored on a ramdisk?
 
Wow, I was skeptical when I read about it, but it really is noticeably faster! The RAM hit is well worth it.

I wonder if IE would go this fast if the temp files were stored on a ramdisk?

While technically the answer is "yes" about the IE question, there's a problem with doing that. You'd need to create a cache of a specific size, and you set that using the IE options of course. That creates the Temporary Internet Files directory where all that stuff gets tossed into, and you can move the location of that folder to the RAMdisk if you create one.

The problem comes from how IE works in terms of downloading data. The IE cache works on the principle of First In Last Out, meaning when new content comes in it's pushed into the cache, and the oldest content gets pushed out. That's not so much a big deal with the usual images, HTML files, Flash banners, etc that you encounter in regular surfing.

What happens if you decide to download a file, however, that might be larger than the IE cache? A lot of crap, basically. Take this example:

Say you create a 512MB RAMdisk and move the Temporary Internet Files folder over to that RAMdisk, and you set the options in IE to limit the cache size to 255MB. Then let's say you decide to download an Ubuntu ISO (roughly 695MB) and you for some reason use IE to do the downloading.

IE stores it's download files - all of them - in that Temporary Internet Files cache, and working on the FILO principle, it will start pushing data out of the folder to make room for that ISO that's now coming in. When it gets to about 255MB, the download will stop, IE won't tell you it didn't finish the download, and you'll be thinking you've now got the full 695MB ISO. You can test this stuff yourself, actually.

Hence, doing big downloads with IE is a no-no, and very impractical, especially if you attempt to use a RAMdisk for the Temporary Internet Files cache.

Firefox and Opera don't use this scheme for downloading - IE downloads a file to one location (the cache) and then moves it out of the cache to the actual target destination you chose when you started the download. Firefox and Opera, however, do downloads direct to the target destination and create the .part files that allow for resuming broken downloads, etc.

I sure hope Microsoft finally addresses the shitty download "manager" that IE comes with. It needs revamping, seriously, it always has as it's effectively useless.

You're better off using Firefox or Opera if necessary, and if you have big downloads, use a proper download manager if you must stick with IE alone.

Hope this helps...
 
It is Firefox 3, just updated and in beta, it'll be an official Firefox 3 update eventually...
 
Back
Top