Closed Bug 1215300 Opened 10 years ago Closed 8 years ago

Experiment with enabling the global hang detector for the chrome process under e10s

Categories

(Firefox :: General, defect, P5)

Product:
Firefox
Component:
General
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
e10s + ---
firefox44 --- affected

People

(Reporter: jimm, Unassigned)

References

(Blocks 1 open bug)

Details

We have a hang detector that was implemented a few years ago. It was designed to detect native message processing hangs and under certain circumstances, crash the browser and generate a crash report so we could investigate hang issues. We only turned this on for a brief time, and afaict never really did much else with it. Now that content has moved into a separate process we should experiment with turning this on again in the chrome process, in the hope that we can use it to catch cross-process messaging hangs on Windows. bug 429592 - hang detector development plus blocking bug list of hangs bug 705748 - disable bug
tracking-e10s: --- → ?
An alternate goal here: use this code to detect deadlocks and report them via telemetry.
Blocks: e10s-perf
tracking-e10s: ? → +
Priority: -- → P5
The patch in bug 1228437 enables the hangmonitor in e10s content processes
BHR seems to be working just fine.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.