Catching an error and dumping it to the text console just isn't nice. The compose window does this if it has an issue whilst opening. It displays a pretty dialog, but that's not much help to the user. The code has support for printing an error message to the string, and all our locales do as well, but we just end up printing ""... I think a chrome error in the dialog is likely to scare users - especially if its intermittent or rare, so just put the error into the error console, and if we get someone having persistent problems, then we can point them in the right direction. I've got two patches to do this, one to change the string on trunk, the second to just change the dump location on the TB 3.0.x builds.

Phil: review ping.

Comment on attachment 429693 [details] [diff] [review] 3.0 branch patch looks reasonable...

Checked in the trunk patch: http://hg.mozilla.org/comm-central/rev/884335fd11a0

Comment on attachment 429693 [details] [diff] [review] 3.0 branch patch a=Standard8 for minor correctness fix that should help with debugging issues with users of released builds.

Checked into 1.9.1: http://hg.mozilla.org/releases/comm-1.9.1/rev/0ba3c6dfdada