gecko-dev/js
Kris Maglione 6e74abe6ee Bug 1403348: Add debugging assertions for more AsyncStartup failure modes. r=baku
Since we don't currently know where or how loading the service is failing, we
need logging in two places:

1) In ServiceWorkerRegistrar, which will tell us about any JS errors that
occur in the factory constructor.

2) In the XPConnect module loader, which will tell us about any JS errors
which happen while loading the top-level module script.

If the load fails due to a non-JS error, we'll simply get a nsresult failure
code, which well be less informative, but will still tell us something about
the failure mode.

MozReview-Commit-ID: 1CsDegJfiho

--HG--
extra : rebase_source : c998e0393d3cb8aca008da47dfce985d0c3affb6
2017-10-29 18:17:34 -07:00
..
ductwork/debugger
examples
ipc Bug 1406570 - Rooting improvements, r=jonco,bz 2017-10-09 10:59:02 -07:00
public Bug 1411302 - Don't try and OOM test worker threads r=jandem 2017-10-27 15:52:43 +01:00
rust merge mozilla-central to autoland. r=merge a=merge 2017-10-24 23:59:14 +02:00
src Bug 1412868: Remove Gecko_GetLookAndFeelSystemColor from the static analysis whitelist. r=manishearth 2017-10-30 08:47:01 -07:00
xpconnect Bug 1403348: Add debugging assertions for more AsyncStartup failure modes. r=baku 2017-10-29 18:17:34 -07:00
ffi.configure
moz.build Bug 1403322 - schedule jsreftests inclusively; r=ahal 2017-10-11 17:31:20 +00:00
moz.configure Bug 1405943 - Part 1: Implement Pipeline Operator |>. r=arai 2017-10-17 00:10:00 -04:00