dom/browser-element/mochitest/priority/CAUTION@deefc01c0e14 (annotated)
dom/browser-element/mochitest/priority/CAUTION
Thu, 15 Jan 2015 21:03:48 +0100
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Thu, 15 Jan 2015 21:03:48 +0100
- branch
- TOR_BUG_9701
- changeset 11
- deefc01c0e14
- permissions
- -rw-r--r--
Integrate friendly tips from Tor colleagues to make (or not) 4.5 alpha 3;
This includes removal of overloaded (but unused) methods, and addition of
a overlooked call to DataStruct::SetData(nsISupports, uint32_t, bool.)
| michael@0 | 1 | A word to the wise: |
| michael@0 | 2 | |
| michael@0 | 3 | You must ensure that if your test finishes successfully, no processes have |
| michael@0 | 4 | priority FOREGROUND_HIGH. |
| michael@0 | 5 | |
| michael@0 | 6 | If you don't do this, expect to see tests randomly fail with mysterious |
| michael@0 | 7 | FOREGROUND --> FOREGROUND priority transitions. |
| michael@0 | 8 | |
| michael@0 | 9 | What's happening in this case is that your FOREGROUND_HIGH process lives until |
| michael@0 | 10 | the beginning of the next test. This causes the process started by the next |
| michael@0 | 11 | test to have low CPU priority. Then the FOREGROUND_HIGH process dies, because |
| michael@0 | 12 | its iframe gets GC'ed, and we transition the new test's process from low CPU |
| michael@0 | 13 | priority to regular CPU priority. |
| michael@0 | 14 | |
| michael@0 | 15 | Ouch. |
