Since discovering that Firefox 4 Beta 13 is stable, I have spent less time with Firefox 3·6, the buggiest, most oft-crashing program I have ever used in 30 years of computing.
But I used it today enough times to net myself ﬁve crashes, though this is above average. The ‘unmark purple’ bug that plagued me for so long has disappeared, which indicates it was an error with an extension (Flash, maybe?), and the average of four per day has decreased to two to three (on the days I use Firefox 3·6 exclusively).
However, since the ’quake, I have still netted a number of errors, and apart from one, there is no pattern to them. Here are the last 13 on this machine (I’ve used it a bit more on my laptop, which doesn’t have 4 Beta):
1 × [@ nsTArray
1 × [@ InterlockedCompareExchange ]
1 × [@ PR_AtomicDecrement | nsSupportsCStringImpl::Release() ]
1 × [@ hang | mozilla::plugins::PPluginScriptableObjectParent::CallHasProperty(mozilla::plugins::PPluginIdentifierParent*, bool*) ]
1 × [@ hang | ntdll.dll@0xe514 ]
1 × [@ nsRuleNode::WalkRuleTree(nsStyleStructID, nsStyleContext*, nsRuleData*, nsCSSStruct*) ]
1 × [@ WrappedNativeProtoMarker ]
1 × [@ F_592283983_____________________________________________ ]
1 × [@ nsExpirationTracker
I have no idea what any of this means, but to the layman it suggests the gremlins are everywhere in the program. (The defence by Firefox proponents in claiming that post-3·5 versions are the most stable releases falls on deaf ears here: 3·0 and 3·6·10 crashed far less often.)
I’ll sure be glad when Firefox 4 rolls out, and I have been really impressed by the bug-ﬁghting and beta-testing programmers. They have actually listened to what I have to say and conﬁrmed that most of the bugs I have reported existed. It’s already a darned sight better than Chrome and its nearly-every-session ‘Aw, snap’ pages, of which no screen shot can be taken.
But based on the above crashes, there is, of course, no mystery on why Chrome’s market share has increased and Firefox’s has decreased. Chrome crashes, but not as often—and most won’t care about its typographic problems or the lack of support. Mozilla needs to get 4 out ASAP: the more 3 crashes—and judging by the comments in Bugzilla, the rate of crashing remains remarkably high—the more likely users will hop over to the competition.