dom/browser-element/mochitest/priority/CAUTION@ac0c01689b40
dom/browser-element/mochitest/priority/CAUTION
Thu, 15 Jan 2015 15:59:08 +0100
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Thu, 15 Jan 2015 15:59:08 +0100
- branch
- TOR_BUG_9701
- changeset 10
- ac0c01689b40
- permissions
- -rw-r--r--
Implement a real Private Browsing Mode condition by changing the API/ABI;
This solves Tor bug #9701, complying with disk avoidance documented in
https://www.torproject.org/projects/torbrowser/design/#disk-avoidance.
1 A word to the wise:
3 You must ensure that if your test finishes successfully, no processes have
4 priority FOREGROUND_HIGH.
6 If you don't do this, expect to see tests randomly fail with mysterious
7 FOREGROUND --> FOREGROUND priority transitions.
9 What's happening in this case is that your FOREGROUND_HIGH process lives until
10 the beginning of the next test. This causes the process started by the next
11 test to have low CPU priority. Then the FOREGROUND_HIGH process dies, because
12 its iframe gets GC'ed, and we transition the new test's process from low CPU
13 priority to regular CPU priority.
15 Ouch.
