46 bytes, text/x-phabricator-request
|Details | Review|
Apparently this was fixed once before, but regressed when we switched to Spidermonkey promises, which I unfortunately did not notice until after I fixed it again. Our unhandled promise rejection reporter tries to avoid undefined behavior by only reporting rejections for native error objects, so that it doesn't have to access JS properties which might run arbitrary code or bring dying objects back to life. Unfortunately, it only currently handles native JS ErrorObjects, and not DOM/XPC Exceptions. We probably don't really need this anti-sniffing behavior anymore, since we no longer report unhandled rejections during finalization. But it's just as easy to special case DOM/XPC Exceptions as it is to remove those guards, so I'm going the safe route for now.
Comment on attachment 9003912 [details] Bug 1486130: Fix reporting of unhandled DOMException rejection values. r=smaug Olli Pettay [:smaug] has approved the revision.
Attachment #9003912 - Flags: review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/7ccc1c8a7abeefd54bc4cf9a5d0eef23681c924a Bug 1486130: Fix reporting of unhandled DOMException rejection values. r=smaug
https://hg.mozilla.org/integration/mozilla-inbound/rev/ee4af6d31e69542f53aee91cb126e3d2a85691de Bug 1486130: Follow-up: Ignore extra console message on OS-X. r=bustage,test-only
You need to log in before you can comment on or make changes to this bug.