Javascript Stacktrace update

最新推荐文章于 2025-11-30 14:07:43 发布

原创最新推荐文章于 2025-11-30 14:07:43 发布 · 155 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#JavaScript #Chrome #Opera #IE #Safari #ViewUI

内存泄露相关专栏收录该内容

16 篇文章

订阅专栏

本文介绍了作者自2008年启动的JavaScript堆栈跟踪项目的最新进展，包括更新后的浏览器兼容性和GitHub上的开源代码。该项目旨在为缺乏良好调试工具的浏览器提供额外的调试能力。

I started a Javascript Stacktrace project back in August 2008. The idea was to give additional debugging power to browsers where you don’t have good tools to work with. I’d like to give you an update on where the project is today.

Lately, I’ve been working on updating my old script. Since it was written, we’ve seen lots of major browser releases and the introduction of the V8 Javascript engine used byGoogle Chrome.

Updated browser compatibility

Browsers that are fully-supported and well-tested:

Firefox (and Iceweasel) 0.9+
UPDATE: Chrome 1+ now perfectly supported
Safari 3+
IE 5.5+
Opera 9+
Konqueror 3.5+
K-Meleon 1.5.3+
Epiphany 2.28.0+

Browsers that are supported in almost all cases but not as well-tested:

Chrome 1+ – One bug (feature?) that may be in Chrome reporting functions as anonymous when they aren’t. HOWEVER, Chrome’s stack gives us line numbers AND column numbers, so we can see exactly where our problem is – even in minified Javascript! Sweet!Chrome 1+ now fully supported.
Opera 7-8 – Opera is dead to me now. Opera 10+ has removed the error.stack info we needed and introduced error.stacktrace, but it seems very unstable. Argh.

More info about compatibility can be shown with theBrowserShots of the test suite.

Now socially coded

I’m not going to post the code here because the source and tests are now on the javascript-stacktrace project on GitHub. You can download it here.

Follow it, file bugs, and make comments there. If you have improvements to make, please fork the project and then contact me or do a “push request”. I’ll make sure you get credit ;)

UPDATE: Øyvind Sean Kinsey has added memoization (caching the implementation) for the mode and XHR bits as well as the ability to pass an existing Javascript Error and get a stacktrace. We’re working on tests and you should see project updates soon. Thanks, Øyvind!

var lastError;
try {
    // error producing code
} catch(e) {
   lastError = e;
   // do something else with error
}

// later...
printStackTrace({e: lastError}); //Returns stacktrace from lastError!

Try it out!

The code is in use on my blog. Click here to give it a spin.

function foo() {
    var blah;
    bar("blah");
}
 
function bar(blah) {
    var stuff;
    thing();
}
 
function thing() {
    if (true) { //your error condition here
        var st = printStackTrace();
        alert(st.join("\n\n"));
    }
}
 
foo();

Random note: one cool suggestion I saw was to assign printStackTrace to window.onerror. Pretty brilliant if you ask me.

I want to thank the guys who contributed to the script:Luke Smith, Loic Dachary and Johan Euphrosine.

I could use a bit of help getting the Chrome and Opera bugs worked out. I’m sure some of you guys who remember how to write software can help. Suggestions and whinings are welcome as long as they don’t get out of hand in the comments.

Javascript Stacktrace on GitHub