As mistakes go, this is a pretty common one. When it happens, this is all we print: System JS : ERROR (null):0 uncaught exception: 2147746065 Improving the error handler in xpconnect seems hard since we don't have any kind of exception object to attach a stack trace or filename/line number information to. However, we can at least print something useful when it happens.
Attachment #814262 - Flags: review?(jwalden+bmo)
Attachment #814262 - Flags: review?(jwalden+bmo) → review+
Assignee: nobody → wmccloskey
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
You need to log in before you can comment on or make changes to this bug.