Perhaps there's a better way to control out-of-control render processes. Chromium implements this dialog for unresponsive pages:
This implies that Chromium lets you kill a page/render process. On a side note: An infinite JS loop does not trigger this dialog. What would be useful would be a way to expose the API from Chromium that enables the killing of the render process at any time from the main UI thread / browser process. Do you think this would be a more elegant solution to this problem, than exposing an API to gather render process IDs and manually kill them with TerminateProcess afterwards?