Closed Bug 1530617 Opened 5 years ago Closed 5 years ago

Allow disabling BackgroundHangMonitor on Nightly

Categories

(Toolkit :: Telemetry, defect, P1)

defect

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: mikokm, Assigned: mikokm)

References

Details

Attachments

(1 file)

BackgroundHangMonitor uses around 10% CPU on my Windows machine for stack collection, when I am running heavy benchmarks.

It would be nice to be able to disable it for more stable benchmarks.

Setting "P1" as it's currently being worked on.

Priority: -- → P1

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:miko, could you have a look please?

Flags: needinfo?(mikokm)
Pushed by mikokm@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/27accf858b3d
Add pref for disabling BackgroundHangMonitor r=froydnj
Flags: needinfo?(mikokm)
Assignee: nobody → mikokm
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68

Miko, could you clarify why this only disables BHR in content processes? It's not altogether clear to me from the patch or this bug.

Flags: needinfo?(mikokm)

(In reply to Doug Thayer [:dthayer] from comment #6)

Miko, could you clarify why this only disables BHR in content processes? It's not altogether clear to me from the patch or this bug.

The motivation behind adding this pref was to get cleaner profiles during benchmarking. On my machine the content process was the only one where this stack collection was taking excessive CPU time.

Flags: needinfo?(mikokm)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: