On 20/11/2013 01:30, Boris Zbarsky wrote: > On 11/19/13 12:26 PM, Anne van Kesteren wrote: >> On Tue, Nov 19, 2013 at 5:17 PM, Boris Zbarsky <bzbar...@mit.edu> wrote: >>> It's been the case since late August, though the behavior is a bit >>> different: only thrown Errors or rejections with an Error are logged, not >>> arbitrary rejections. >> >> Why are we doing it only for Error objects? > > The intent was to catch cases of code throwing unexpected exceptions > inside a promise callback (which promises catch and turn into a > rejection) and report those. > > We could report all rejections, but I'm a bit leery of adding so much > noise that people start ignoring the report altogether; a common problem > in the past.
Currently, I'm getting this in the Error Console a few seconds after startup: Thu Nov 21 2013 13:23:23 Error: A promise chain failed to handle a rejection. Date: Thu Nov 21 2013 13:23:13 GMT+0800 (Malay Peninsula Standard Time) Full Message: [object StopIteration] Full Stack: JS frame :: resource://gre/modules/osfile/osfile_async_front.jsm :: withIterator :: line 1032 JS frame :: resource://gre/modules/Promise.jsm :: <TOP_LEVEL> :: line 767 JS frame :: resource://gre/modules/Promise.jsm :: <TOP_LEVEL> :: line 531 native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0 This is singularly unhelpful. Can we have better error stacks? Phil -- Philip Chee <phi...@aleytys.pc.my>, <philip.c...@gmail.com> http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
