Fwd: [Ann] Displaying uncaught asynchronous errors

Gavin Sharp gavin at gavinsharp.com
Tue Oct 15 18:33:50 UTC 2013

---------- Forwarded message ----------
From: David Rajchenbach-Teller <dteller at mozilla.com>
Date: Tue, Oct 15, 2013 at 3:34 AM
Subject: [Ann] Displaying uncaught asynchronous errors
To: dev-platform <dev-platform at lists.mozilla.org>

I am happy to inform you that we have recently landed Bug 903433, which
ensures that uncaught errors or rejections in Promise.jsm or Task.jsm
are now displayed.

So, from now on, if you are attempting to debug asynchronous code using
Promise.jsm/Task.jsm, don't forget to look in the browser console
output, you should find the error that you are looking for.

Additionally, since bug 908955 landed, Promise.jsm/Task.jsm will dump()
any programming error (e.g. TypeError, SyntaxError and the ilk)
immediately, regardless of whether it is caught. So, keep an eye on your
stderr, too.

Both changes should make debugging async code much easier.


David Rajchenbach-Teller, PhD
 Performance Team, Mozilla
dev-platform mailing list
dev-platform at lists.mozilla.org

More information about the firefox-dev mailing list