Jan0809Jan 08, 09
I've been using Firefox on Leopard for a while and it's always had one very obvious bug. Every time Firefox displays a connection error or DNS error page, the browser grinds to a halt and is irrecoverable for around 2 minutes. This has become even more annoying because I am now working throughout the day on my Mac instead of only in the evenings. What part of the simple XHTML and CSS used on these error pages is triggering the stall? It doesn't seem to be a memory leak, because the CPU process doesn't steadily increase when an error page is open.
I'm interested to hear if others have experienced the same problem, perhaps leave a comment.