Mozilla Branches for 0.9.8

Wednesday January 23rd, 2002 today branched for Mozilla Milestone 0.9.8, as well as opened the tree for 0.9.9 checkins. Look for branch builds to start sometime later this week, as early as tomorrow. (While a certain site believes that without builds, you can't have a branch, that is not true.) Pre-0.9.9 trunk builds will start tomorrow, or possibly tonight. See our earlier story for what's new in 0.9.8.

#39 Re: Re: A harsh test on 2002012203 build

by macpeep

Saturday January 26th, 2002 4:54 AM

You are replying to this message

Like someone already pointed out, it works fine in IE 6.0. The browser and rest of the system stay 100% responsive and after seeing a couple of hundred frames or so (no, I didn't actually count them, but the window was pretty full of them), I just clicked stop to end the loading. Resizing the frames also works very well.. No noticable slowdown.

While the frames were loading, I opened up another IE window and surfed over to <> Worked great, except that it took about 2 seconds to open the new browser window due to the high CPU usage from loading the recursive frames.

I'm not really sure what exactly this test is supposed to prove. "Too much of" types of crashes or slowdowns will probably happen to any software at some point. Make an 80 GB long HTML file and see how it renders in Mozilla. Probably will cause some slowdown and/or crash. But so what? However, this recursive frame test doesn't actually seem to cause much else than some slowdown until you give the browser mercy and end the loading. But even if browsers crashed, it only proves instability in extreme situations.

What's interesting is stability under NORMAL conditions. At least that's what I assume most users would care about. You know, not crashing when you drag a bookmark to another folder or browsing a perfectly normal and common site.. I think those kinds of crashers should have a much higher priority than something like this.