So the whole-browser-takedown seems to be the same underlying issue (1) when you load the testcase and (2) after you restart. We're essentially letting a content process consume all of the parent process's resources. We should probably fix this by addressing that underlying issue (e.g. throttling the rate at which we generate http requests, or something like that?)
Bug 1037984 Comment 27 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
So the whole-browser-takedown seems to be the same underlying issue (1) when you load the testcase and (2) after you restart. We're essentially letting a content process consume all of the parent process's resources (initially in the content process for a tab, and then later in a content process for a thumbnail). We should probably fix this by addressing that underlying issue (e.g. throttling the rate at which we generate http requests, or something like that?)