It's a real problem but it doesn't affect everyone the same way. Many of the issues are related to extensions holding on to references in long gone tabs and Firefox 7 is the first version that will see results from the MemShrink project (you can read about the details in the wiki).

I've had Firefox break the userspace memory barrier (3gb on windows x64) and becoming slow many times before, mostly because of Firebug.

That's my point, actually, except for the part where you say the faster release cycle can not solve this problem. You see, it actually makes development slower (IMO), but everything that makes the cut from a nightly build to a aurora release will be released. You don't get to the point where you have tons of stale, crashy features that need to be finished "yesterday" and keep holding up the release date. Even traditionally unstable nightly can be used as a main browser now because big features are being developed in parallel synched branches (ux, ti, ...) that are only merged to the nightly if they are stable enough.

I'd love to know why FF6 doesn't work for you.

You still have FF3.6. What are you complaining about? You still have chrome, opera, IE6~9 as alternatives. Heck, you like stability so much why aren't you using debian? Their fully supported browser version is based on firefox 3.5, and I'm sure you'll prefer lenny's release because it's based on Firefox 3 and fully patched.

This anti-fanboy atitute is what makes me go into fanboy mode.

There is one for FF3.6. Firefox 3.6.23 will be released September 27th: https://wiki.mozilla.org/Releases/Firefox_3.6.23
This is being maintained due to user pressure, I think. But it is nonetheless.

There were more than a few firefox4 betas and in the meantime all new development nearly stopped. The road to even get to a first beta was full of dropped features, nightly versions that were unusable for a long time. And it took years to release......

Unless you need FF3.6 because of some internal website or some specific add-on there are no reasons (other than personal preference) to be using 3.6 instead of 6.

They do. There are 4 branches: nightly, aurora, beta, "final". Every one of them follows a 6 six week cycle. I'm currently running firefox 9 nightly, for example, and current versions 8 and 7 are very stable already.

You have to take into consideration that, in browsers, implementing or fixing a particular css/html feature is prone to break existing apps that rely on the wrong behavior. IE6 is still used in many environments for this reason exactly, but in the case of Firefox changes are very small between releases.

Type "about:support" in the address bar and press enter.

There's also "about:" if you care to try.

Firefox is using opengl->directx conversion by default using google's Angle library. There's a pref to turn native support ON but it's not enabled by default and, at least in my case, it's not working.

That's the landing page you get after installing it.
Try https://www.mozilla.com/en-US/firefox/beta/

Update your graphics card drivers or disable hardware acceleration. They could use a bug report with information you get from when you type about:support in the location bar, though. If it's as bad as you say that card/driver combo should be blacklisted

You need to go there through google to be able to read the answer (hint: HTTP-referrer)
They make this exception because otherwise google wouldn't index them.

This discussion would be over quickly once you understand that this isn't a IIS bug.
Anyway, put any of these hacked websites running under Apache/Mono and voilá, an Apache vulnerability under your definition.

Thanks for playing. ;)

It is. Often. Here's an example search within slashdot for wordpress vulnerabilities.

You should know that these vulnerabilities will also work when running wordpress under IIS.
The server software has nothing to do with it, it's a framework issue.

Yes, there's a reason: you're filtering the information you get.
That particular issue you are pointing out was an SQL Injection attack and IIS/asp.net can't do anything about that.

Recent firefox progress in my machine:
- Firefox 3.6: 1063.0ms +/- 4.9%
- Firefox 4.0b4pre (today's build): 622.6ms +/- 12.0%

These are with the same engine, btw. Jaegermonkey is not in nightly builds yet.
It doesn't take much more to make you bound to DOM operations in normal webapps.

PS: sunspider 0.9.1 is also available

Working on it. FTA:

A difficult step, yes, but without creating the market private companies won't jump in and invest.

Your firewall is probably blocking the plugins process.
Look here for a solution:http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins#Plugin-container