Closed Bug 1793276 Opened 2 years ago Closed 2 years ago

New wpt crashes in /screen-capture/getdisplaymedia.https.html

Categories

(Core :: WebRTC: Audio/Video, defect, P2)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1788563

People

(Reporter: wpt-sync, Unassigned)

References

Details

(Whiteboard: [wpt])

Syncing wpt PR 36128 found new crashes in CI

Affected Tests

  • /screen-capture/getdisplaymedia.https.html [wpt.fyi]: CRASH [Gecko-windows10-32-2004-qr-debug, Gecko-windows10-64-2004-qr-debug], OK [Gecko-linux1804-64-qr-debug, Gecko-linux1804-64-qr-opt, Gecko-windows10-32-2004-qr-opt, Gecko-windows10-64-2004-qr-opt, GitHub], SKIP [Gecko-android-em-7.0-x86_64-lite-qr-opt-geckoview, Gecko-android-em-7.0-x86_64-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-qr-debug-isolated-process-geckoview, Gecko-android-em-7.0-x86_64-qr-opt-geckoview]

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

Getting the crash signature into these bug reports is a TODO; sorry

These updates will be on mozilla-central once bug 1793052 lands.

Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.

This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/

If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.

Andreas, is this something you'd be able to look at?

Severity: -- → S3
Flags: needinfo?(apehrson)
Priority: -- → P2

The crashes mentioned here and in bug 1793052 are bug 1788563. It is debug-only and triggered by one of the RTC_DCHECKs in MouseCursorMonitorWin::Init, can't really say which.

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(apehrson)
Resolution: --- → DUPLICATE
Severity: S3 → S4
You need to log in before you can comment on or make changes to this bug.