User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 Implant of one of the best diagnose add-on crashes. This will help many people telling them why the browser has crashed and tell them to ask help on mozilla forum or submit a bug on bugzilla. Can be found at https://addons.mozilla.org/en-US/firefox/addon/11217 Reproducible: Always

I'm not going to close this bug, but, imo, its a bad idea... This addon itself can cause crashes, and if it was, then a whole new version of firefox would have to be rolled out, because almost 100% of the users would be crashing...

cc'ing dave, the developer of the addon. I believe that there is already a bug in implementing the features in the addon.

If not the addon something similar will be great to have in firefox in near future,many users will be very very happy with this as can help them prevent crashes,and many other problems,and they will know where to ask help,report bugs,it will be something very interesting.

Could also be duped to bug 336872 or similar, but this is as good as any. (In reply to comment #1) > I'm not going to close this bug, but, imo, its a bad idea... This addon itself > can cause crashes, and if it was, then a whole new version of firefox would > have to be rolled out, because almost 100% of the users would be crashing... Er... where's this apocalyptic scenario coming from? If you can get a crash out of CRH then file a bug here (CCing me of course). I don't have any binary components in there, not just for the obvious reason but because I don't need them. If CRH crashes then it's going to be a JavaScript engine bug. CRH is pure JS. (In reply to comment #2) > cc'ing dave, the developer of the addon. I believe that there is already a bug > in implementing the features in the addon. Yeah, there's a couple bug reports open about CRH features. Another is bug 442519. Fortunately, though, many of my features are being made progressively obsolete. Crashable components (which CRH has trouble diagnosing) will be banned for Firefox 3.6, crashable extensions (binary modules) will be banned at some point after that, and plugins will eventually be run out of process so as to not crash all of Firefox with them (and they'll be able to announce their crashes independently). One of these days I'll find the time to actually update this thing and then look into at least porting the about:crashes augmentation over or more.

(In reply to comment #5) > Could also be duped to bug 336872 or similar, but this is as good as any. > > (In reply to comment #1) > > I'm not going to close this bug, but, imo, its a bad idea... This addon itself > > can cause crashes, and if it was, then a whole new version of firefox would > > have to be rolled out, because almost 100% of the users would be crashing... > > Er... where's this apocalyptic scenario coming from? If you can get a crash out > of CRH then file a bug here (CCing me of course). I don't have any binary > components in there, not just for the obvious reason but because I don't need > them. If CRH crashes then it's going to be a JavaScript engine bug. CRH is pure > JS. > Hm... I misunderstood the request itself...

Not a dup of bug 408721.