Closed Bug 1611053 Opened 6 years ago Closed 6 years ago

Add profiler marker for XPCJSContext::InterruptScript

Categories

(Core :: Gecko Profiler, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
mozilla76
Tracking Status
firefox76 --- fixed

People

(Reporter: squib, Assigned: squib)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Currently, there's no profile marker emitted for XPCJSContext::InterruptScript. There are a few situations where it'd be helpful to see the presence (or absence!) of this call: when debugging long-running JS that you'd expect to trigger the slow script notification, or to identify if InterruptScript is correlated with any other perf issues. In particular, this would be useful for helping to diagnose bug 1606386, especially comment 9.

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:squib, could you have a look please?
For more information, please visit auto_nag documentation.

Flags: needinfo?(jporter+bmo)

Whoops, I got pulled over onto Fenix stuff and this slipped off my radar! I'll try to get this landed in the next day or so...

Pushed by jporter@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/05881652e940 Add profiler marker for XPCJSContext::InterruptScript; r=gerald
Pushed by jporter@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/df5cc0983031 Add profiler marker for XPCJSContext::InterruptScript; r=gerald
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76

Forgot to clear the needinfo when this re-landed...

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

Attachment

General

Created:
Updated:
Size: