gecko/dom/interfaces
Kyle Huey 1ffb03e8dc Bug 1179909: Refactor stable state handling. r=smaug
This is motivated by three separate but related problems:

1. Our concept of recursion depth is broken for things that run from AfterProcessNextEvent observers (e.g. Promises). We decrement the recursionDepth counter before firing observers, so a Promise callback running at the lowest event loop depth has a recursion depth of 0 (whereas a regular nsIRunnable would be 1). This is a problem because it's impossible to distinguish a Promise running after a sync XHR's onreadystatechange handler from a top-level event (since the former runs with depth 2 - 1 = 1, and the latter runs with just 1).

2. The nsIThreadObserver mechanism that is used by a lot of code to run "after" the current event is a poor fit for anything that runs script. First, the order the observers fire in is the order they were added, not anything fixed by spec. Additionally, running script can cause the event loop to spin, which is a big source of pain here (bholley has some nasty bug caused by this).

3. We run Promises from different points in the code for workers and main thread. The latter runs from XPConnect's nsIThreadObserver callbacks, while the former runs from a hardcoded call to run Promises in the worker event loop. What workers do is particularly problematic because it means we can't get the right recursion depth no matter what we do to nsThread.

The solve this, this patch does the following:

1. Consolidate some handling of microtasks and all handling of stable state from appshell and WorkerPrivate into CycleCollectedJSRuntime.
2. Make the recursionDepth counter only available to CycleCollectedJSRuntime (and its consumers) and remove it from the nsIThreadInternal and nsIThreadObserver APIs.
3. Adjust the recursionDepth counter so that microtasks run with the recursionDepth of the task they are associated with.
4. Introduce the concept of metastable state to replace appshell's RunBeforeNextEvent. Metastable state is reached after every microtask or task is completed. This provides the semantics that bent and I want for IndexedDB, where transactions autocommit at the end of a microtask and do not "spill" from one microtask into a subsequent microtask. This differs from appshell's RunBeforeNextEvent in two ways:
a) It fires between microtasks, which was the motivation for starting this.
b) It no longer ensures that we're at the same event loop depth in the native event queue. bent decided we don't care about this.
5. Reorder stable state to happen after microtasks such as Promises, per HTML. Right now we call the regular thread observers, including appshell, before the main thread observer (XPConnect), so stable state tasks happen before microtasks.
2015-08-11 06:10:46 -07:00
..
apps Bug 1182347 - Migrate existing code away from .cookieJar. r=sicking,r=allstars.chh 2015-07-14 19:56:33 -07:00
base Bug 1179909: Refactor stable state handling. r=smaug 2015-08-11 06:10:46 -07:00
canvas
core
css
events Bug 1119074 - If we're stopping event propagation from XUL popups, also stop them from crossing process boundaries r=smaug,felipe 2015-05-25 16:54:13 -04:00
gamepad
geolocation
html Backed out changeset f5f3827ffcf1 (bug 1166910) for bustage 2015-07-01 08:19:28 +02:00
json
notification Bug 1114554 - Patch 4 - ServiceWorkerRegistration.getNotifications() on main thread. r=wchen 2015-06-25 18:50:25 -07:00
offline
permission
push Bug 1188686 - Clear push subscriptions when forgetting about site. r=kitcambridge 2015-07-29 11:33:48 -07:00
range
security Bug 1139297 - Implement CSP upgrade-insecure-requests directive - csp changes (r=sstamm) 2015-07-10 09:13:54 -07:00
settings
sidebar Bug 940206 - Implement Navigator.registerContentHandler and Navigator.registerProtocolHandler for e10s. r=dao 2015-07-31 17:03:37 -07:00
smil
storage
stylesheets
svg
traversal
xbl
xpath
xul