Open Bug 1624899 Opened 4 years ago Updated 3 years ago

Firefox debug build completely hangs or quits when starting a webRTC call

Categories

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

All
Windows 10
defect

Tracking

()

Tracking Status
firefox75 --- wontfix
firefox76 --- wontfix
firefox77 --- fix-optional

People

(Reporter: bmaris, Unassigned)

Details

(Keywords: regression)

Affected versions

  • Firefox 76.0a1 debug build
  • Firefox 75.0b8 debug build

Affected platforms

  • Windows 10 64bit

Unaffected platforms

  • Ubuntu 18.04 64bit
  • macOS 10.15

Steps to reproduce

  1. Download a debug build of latest Nightly 76.0a1 or 75.0b8:
    https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&revision=2abd352490a4bf2e3a9118b154c0e351c0bad314
  2. Visit the following fiddle https://jsfiddle.net/jib1/LbtxeLvw/
  3. Click Start Camera! (a webcam is required for this step)
  4. Click Allow on the permission notification

Expected result

  • Video and Microphone recording starts

Actual result

  • Firefox either hangs (but the microphone recording is working) or the browser will just quit.

Regression range

  • Not sure if this is a recent regression, will have to dig a bit here and see. Will return with some results ASAP.

Additional notes

  • This is the output from the terminal before Firefox is shutting down:
# Fatal error in /builds/worker/checkouts/gecko/media/webrtc/trunk/webrtc/modules/video_capture/windows/sink_filter_ds.cc, line 723
# last system error: 0
# Check failed: rtc::internal::AnnounceOnThread::IsCurrent(&capture_checker_)
Flags: needinfo?(dminor)
Has Regression Range: --- → yes
Has STR: --- → yes

Bug 1552755 was an update of third party code. I'll check to see if there is a fix for this upstream.

Assignee: nobody → dminor
Flags: needinfo?(dminor)
Priority: -- → P3
Priority: P3 → P2

This only affects debug builds, so I'm lowering the severity. I'm unable to reproduce this on my Windows laptop.

Severity: critical → S4
Priority: P2 → P3
Assignee: dminor → nobody
You need to log in before you can comment on or make changes to this bug.