At the end of the test, test_gpuprocess.js, will call 'controlGPUProcessForXPCShell(false)' which will kill the GPU process.  The GPU process isn't disabled though, so it will be immediately restarted once the GPUProcessManager realizes the process has died. Either we shouldn't bother trying to kill the GPU process at the end of the test, or we should kill and disable it.  http://searchfox.org/mozilla-central/rev/15ce5cb2db0c85abbabe39a962b0e697c9ef098f/toolkit/components/aboutmemory/tests/xpcshell/test_gpuprocess.js#17
The intent for the API was to make the GPU process more testable, i.e. start and kill it arbitrarily. So I think disabling it is the right call.
2 years ago
Attachment #8912238 - Flags: review?(dvander) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/e06e885db07d Disable the GPU process in xpc-shell after we kill it to prevent extra restarts. (bug 1402500, r=dvander)
You need to log in before you can comment on or make changes to this bug.