1152306 - Add "report a bug" button on the slow script notification.

Status: NEW

(Core :: DOM: Core & HTML, defect)

Description

[Nicolas B. Pierron [:nbp] {away}]

Currently we have a notification to inform the user that his browser is slow, and the only action that we are suggesting is that this issue might be related to the content of one of the page that is open on his browser.

I think that especially for chrome:// URLs, and maybe for any web traffic we should offer the possibility to let our users tell us which script/website is slow.

I suspect that even if we are likely to have a lot of false positive, we also are likely to highlight huge performance regressions which are not covered by any benchmark yet.

Crashes, as well as performance regressions, are a valid reasons for doing backouts.  For crashes, we are getting crash reports which are collected on crash-stat.  For performance, we have no report except for pre-instrumented telemetry probes.

I think we could make something similar to crash-stat by adding a button on the slow script notification, which turns on the profiler and reports these as we report backtraces in crash-stat.

Comment 1

[:Gijs (he/him)]

TBH, I think that because of nested event loops for dialogs, chrome:// URIs in that dialog are almost always a bug in how we detect "slowness", rather than issues with the script. I don't think this is worth doing. But anyway, all the implementation of this dialog lives in Core (nsGlobalWindow and the JS engine, last I looked), so this bug should, too.