Pausing content JS can already be done using the slow script debug machinery. That machinery runs from inside a *JS* interrupt, so the trick is to trigger a JS interrupt from off-process. Signals or periodic wakeups, I suppose. Blake didn't like the idea of implementing signal handlers.
We have a hang monitoring thread. You could probably repurpose it to trigger the operation callback at arbitrary times. The hard part would just be hooking everything up properly.
Er, this is for e10s-only, right? I'm not sure how you would do the UI otherwise.
(In reply to Bill McCloskey (:billm) from comment #2) > Er, this is for e10s-only, right? I'm not sure how you would do the UI > otherwise. Yeah, e10s only. I don't know if "Content Processes" was the right module. Would be a nice feature for devs using e10s.
You need to log in before you can comment on or make changes to this bug.