Skip to content

check more thoroughly crash signature affects more than one machine before creating bug #40

Description

@Archaeopteryx

The bot files bugs for crash reports which are very, very unlikely to see action because of low crash volume. Suggestion: Avoid filing bugs in following the scenarios:

  • Bug 2048951: [@ vivante_dri.so] has 3 crash reports from 2 installs but all crash reports are for machines with the graphics device VeriSilicon Corporation | Vivante GC8400XS. If it's a hardware-bound issue, there should only be a bug for more affected installs with new reports continuing to come in. Suggestion: 5+ or 10+ crash reports and 3+ of them in the last 2 days.
  • Bug 2048949: amdxx64.dll | _tailMerge_hid.dll | amdxx64.dll | delete. 4 crashes from 2 affected devices, maximum 2 reports per build ID, 2 affected graphics devices of the same device class. Could uses the same thresholds like above.
  • Bug 2048950: [@ js::jit::FrameDescriptor::type]. Only reported for release builds, only once per affected install and maximum 5 installs per release. The volume is too low to see prioritization. For comparison: The 200th most frequent bug for Firefox 152.0.1 has 19 crash reports.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions