Perfherder has detected a browsertime performance regression from push 8e1673c94b6c895422160b5ad3ca8b9943cb2541. As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests. Please follow our guide to handling regression bugs and let us know your plans within 3 business days, or the offending patch(es) may be backed out in accordance with our regression policy.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

For more information on performance sheriffing please see our FAQ.

That patch only touches parent process popup code, which doesn't affect pageload, so I don't think it can cause this regression.

Set release status flags based on info from the regressing bug 1824986

This bug was moved into the Performance component.

:alexandrui, could you make sure the following information is on this bug?

• For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
• For memory usage issues, capture a memory dump from about:memory and attach it to this bug.
• Troubleshooting information: Go to about:support, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.

If the requested information is already in the bug, please confirm it is recent.

Thank you.

This is an automated perf alert, removing the NI.

I think we should just close this bug. A 3% LVC regression on it's own without any other changes is not very interesting to act on.