To some extent here, we're struck. The beachballing is Gecko laying out HUGE amounts of text data and reflowing as it gets HUGE chunks of data from the networking library. Gecko has never been good about this, from day one, because it's a recursive descent parser and not an iterative one like we had in NS4.x. The 4.x parser allowed us to say "we're taking too long, go back to the main event loop for a while", but alas Gecko provides no such option because of the way it was written.

The only way to "fix" this is to make gecko work better with large amounts of text. I think there are bugs for this, but they don't get a lot of attention. It's not a common case (except as noted here, and the fix is to fix it by sniffing).

On Dec 9, 2003, at 12:08 PM, paulc wrote:

I find this very much on topic! The issue is that while that "garbage" is filling one's browser window, the browser is dead... as in unable to do anything else. I see it alternating between the arrow with the mini-beachball and the SBBOD (the colored OS pinwheel). Makes it DOUBLY annoying.

--
Mike Pinkerton
Mac Weenie
[EMAIL PROTECTED]

_______________________________________________
Camino mailing list
[EMAIL PROTECTED]
http://mozdev.org/mailman/listinfo/camino

Reply via email to