The video from Screen capture on getUserMedia test page hangs
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Tracking
()
People
(Reporter: obotisan, Assigned: jib)
Details
Affected versions
- Firefox 73.0b3
- Nightly 74.0a1
Affected platforms
- Windows 10 x64
- Windows 7 x86
- macOS 10.15
- Ubuntu 18.04 x64
Steps to reproduce
- Go to https://mozilla.github.io/webrtc-landing/gum_test.html
- Click on the "Screen capture" and select a screen.
- Observe the video.
Expected result
- The video works without issues.
Actual result
- The video hangs.
Regression range
- This is not a regression. I can reproduce the issue on a build from 2019-01-07.
Additional notes
- There is no error thrown in the Console regarding this issue.
- It doesn't matter if the pref layers.acceleration.disabled is set to true or false.
Comment 1•4 years ago
|
||
I'm not seeing a hang but very low FPS (averages 0.2 FPS on my Linux and OS X machines). There is a slider that controls the requested framerate which defaults to zero. If I set it to 30, I get ~30 FPS on my Linux machine as expected.
Jan-Ivar made some changes to the gum_test.html page back in November which might explain the change in behaviour: https://github.com/mozilla/webrtc-landing/commit/5721db2b39bf8294439f892a540316511bd6a1fd. The comments on the page suggest that setting the desired FPS to 0 should result in a default value, so its possible there has been a regression in Firefox with the default value, but I'm almost certain I was using this page in the summer and was getting a reasonable FPS without adjusting anything, and Comment 0 suggests this reproduces with a build from January 7, 2019.
I'm setting this to P3 for now as I think this is just a change in the test page and not a Firefox regression. Jan-Ivar, could you please have a look and let me know what you think?
Assignee | ||
Comment 2•4 years ago
|
||
Yeah I blew the zero detection on frameRate in the test script. Now fixed. PTAL.
Comment 4•4 years ago
|
||
Yes, works for me.
Updated•4 years ago
|
Reporter | ||
Comment 5•4 years ago
|
||
I verified the fix using latest Nightly 74.0a1 and beta 73.0b4 on Windows 10 x64, Ubuntu 18.04 x64 and macOS 10.13. The issue is not reproducing anymore. I think this bug is fixed.
Description
•