[null, {"document_url": "http://asserttrue.blogspot.com/2012/11/firefox-crash-and-burn-syndrome.html", "unformatted_src": "http://3.bp.blogspot.com/-DG9YoR-84NM/ULjI3c1BHOI/AAAAAAAABBk/Q3eXb0MstF0/s1600/Untitled.jpg", "src": "http://3.bp.blogspot.com/-DG9YoR-84NM/ULjI3c1BHOI/AAAAAAAABBk/Q3eXb0MstF0/s1600/Untitled.jpg", "formatted_filename": "Untitled"}, null, null, null, null, null, null, null, null]

Firefox Crash-and-Burn Syndrome My love-hate relationship with Firefox is slowly shifting toward mostly hate. One reason: About every 7 to 10 days, I get a sudden crash where Firefox disappears except for the above dialog. Sometimes the Details button doesn't work. Making me wonder if Mozilla will even get the Crash Report after all.

Clearly, in a situation like this, Firefox is crashing after an unchecked error. (Otherwise why does Mozilla need a complete Crash Report? Why not just get the error code? Answer: There is no error code. The program doesn't know why it quit.) My strong suspicion is that AJAX-intensive sites like Gmail and Twitter are running the program out of memory. Constant client-server AJAX chatter from endless polling is an invitation to memory leakage. (Plus see this post.)

Someday I'll switch to Chrome 100%, but the way I work now is, I use Firefox for business-related browsing and Chrome for personal surfing. I like keeping them separate. I'll continue to use Firefox until the sad day comes when we part company forever. At that point, maybe I'll send flowers and a short, poignant good-bye note. Never to be seen again.
Posted by Kas Thomas at 10:09 AM 


Add a comment. Registration required because trolls.

Total All-Time Pageviews Try Some JavaScript Sometimes it's okay to be a Follower: