When gBrowser.addProgressListener gets called with 2nd argument, we get an uninformative error in the error console: Error: gBrowser.addProgressListener was called with a second argument, which is not supported. See bug 608628. Source File: chrome://browser/content/tabbrowser.xml Line: 1871 How am I supposed to know who was the caller? var caller = Components.stack.caller; throw new Error( "...", caller.filename, caller.lineNumber ); or Components.utils.reportError(new Error( ... ));
NS_ASSERT actually displays the stack in non-release builds: http://mxr.mozilla.org/mozilla-central/source/toolkit/content/debug.js#95
But couldn't you make that error itself in the error console be more informative and make it tell who was the caller?
How I'm tired of these errors! Error: gBrowser.addProgressListener was called with a second argument, which is not supported. See bug 608628. Source File: chrome://browser/content/tabbrowser.xml Line: 1877 And how the f- do I get know who called that gBrowser.addProgressListener with a f-ing second argument? How am I supposed to investigate that f-ing error? Why this bug is still UNCO?
There's still no meaningful error message for this. Took me half an hour to find out which extension caused this error. Playing the "half enabled, half disabled"-game with 50+ extension is really funny...
Created attachment 791314 [details] [diff] [review] patch