Hi,

Not exactly the question, but the correlations that I recall having tried
to figure out manually in the past have been:
* Do the crashes have a specific extension in common, or do all the crashes
have at least one extension from some small set of extensions?
* Are the crashes exclusively or almost exclusively on particular CPU
models?
* Does it look like it's roughly one computer submitting all the reports
for a given crash?

Other than that, I tend to look at the basics like OS and reason.

On Fri, Jun 19, 2026 at 3:38 PM 'Gabriele Svelto' via
[email protected] <[email protected]> wrote:

> [cross-posting to dev-platform and crash-reporting-wg]
>
>    Hiya all,
> as part of the work to overhaul our crash reporting infrastructure we
> were trying to figure out how the correlations data is being used by
> developers and triagers when looking at crash reports. In particular we
> would like to know:
> - Which entries do you find more useful and why? (e.g. reason, DLLs, OS
> version, graphics driver version, etc...)
> - Do you look only at the top entries or do you also find the weaker
> correlations useful?
> - Last but not least, do you look at correlations involving two fields
> at the same time and if yes what's your use-case for them?
>
> Thank you all,
>
>   Gabriele
>
> --
> You received this message because you are subscribed to the Google Groups "
> [email protected]" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion visit
> https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/882e786f-f095-40ec-ae6c-ab207bd0d128%40mozilla.com
> .
>


-- 
Henri Sivonen
[email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAJHk%2B8SgxWZxnCysjrRyqt87uHiPuNt2mLykmJHbCjJqL-tegw%40mail.gmail.com.

Reply via email to