Currently the slow script debug button is hooked up via an XPCom service (nsISlowScriptDebug) during initialization code for the debugger. In e10s, there will be 2 copies of this service for the content and chrome processes. The current way won't work, as the debugger initialization code is in the chrome process and needs to hook up to the service in the content process.
devtools bugs will block the e10s merge to Aurora, but blassey would like them to be tracked by dte10s meta bug 875871, not the tracking-e10s=m6+ flag.
This will be fixed in bug 1118618.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1118618
You need to log in before you can comment on or make changes to this bug.