617944 - Web console should run in a separate process from Firefox, as plugins do

Status: RESOLVED WONTFIX

(DevTools :: General, defect)

Description

[Maniac Vlad Florin (:vladmaniac)]

Build ID: 

Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101207 Firefox/4.0b8pre

Prerequisites: 
Firefox clean profile 

Steps: 

1. Open the console 
2. Type while(1) { console.log("foo log"); } in the command line to pun the process in an infinite loop 

This is an exhaustive test for the console, which of course will cause 
it to block. However, my concern is that while running a simple script 
like that embedded in a webpage in Firefox, it will eventually give you 
the "non-responsive" script error, so Firefox is kind of protected this way. 

Running it in the command line of the console simply blocks the console
as well as the browser, so there is no protection from here. 

It would be nice to have a separate process for the console, or have that 
"non-responsive" script exception to run also for this case.

Comment 1

[David Dahl :ddahl]

Please read the e10s "electrolysis" docs before filing bugs like this. e10s will allow us to have a chrome process and a content process, with async communication between them. The next version of Firefox will implement this (post Firefox 4). Any webpage can do this as the execution context of each page allows JavaScript to do nasty things.

https://wiki.mozilla.org/Firefox/Projects/E10S_Scope_Investigation