Tue, 06 Jan 2015 21:39:09 +0100
Conditionally force memory storage according to privacy.thirdparty.isolate;
This solves Tor bug #9701, complying with disk avoidance documented in
https://www.torproject.org/projects/torbrowser/design/#disk-avoidance.
michael@0 | 1 | var p = new Promise(function(resolve, reject) { |
michael@0 | 2 | // This causes a runnable to be queued. |
michael@0 | 3 | reject(new Error()); |
michael@0 | 4 | postMessage("loaded"); |
michael@0 | 5 | |
michael@0 | 6 | // This prevents that runnable from running until the window calls terminate(), |
michael@0 | 7 | // at which point the worker goes into the Canceling state and then an |
michael@0 | 8 | // AddFeature() is attempted, which fails, which used to result in multiple |
michael@0 | 9 | // calls to the error reporter, one after the worker's context had been GCed. |
michael@0 | 10 | while (true); |
michael@0 | 11 | }); |