For certain recvonly streams, most/all P frames are failing to decode (H264)
Categories
(Core :: WebRTC, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox118 | --- | verified |
firefox119 | --- | verified |
firefox120 | --- | verified |
firefox121 | --- | verified |
People
(Reporter: andrew, Assigned: chunmin)
References
(Regression)
Details
(Keywords: regression)
Attachments
(4 files)
48 bytes,
text/x-phabricator-request
|
diannaS
:
approval-mozilla-beta+
pascalc
:
approval-mozilla-release+
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Steps to reproduce:
This is a regression (good: 7e011293b43, bad: 70417eb0e3b).
The first public Firefox release with this regression is 118.
To repro, using a bad release of Firefox, do the following:
- Go to the URL <redacted>
- Click "View in 3D" button. Wait a few seconds for the page to load.
Actual results:
After the repro steps, the following unexpected results occur with a bad release of firefox (e.g. 118 or 70417eb0e3b):
- You will probably see only a black page. (expected: A video stream of a simple 3D object (teapot) should be shown).
- LMB dragging in the window will have no effect. (expected: Should cause the video stream to show the 3D object being moved with respect to your mouse movement)
- Pressing Alt+L (just once) will also have no effect, or will show a frame or two and then freeze (expected: Should cause the video stream to show the 3D object spinning in place)
- After pressing Alt+L (which ensures that frames are continuously sent from the server), you should notice that about:webrtc shows an increasing number of dropped frames, and very few decoded frames - probably none at all.
Expected results:
With a good release of Firefox (e.g. 117 or 7e011293b43),
- A video stream of a simple 3D object (teapot) will be shown.
- LMB dragging will cause the video stream to show the 3D object being moved with respect to your mouse movement.
- Pressing Alt+L (just once) will cause the video stream to show the 3D object spinning in place.
- After pressing Alt+L (which ensures that frames are continuously sent from the server), you should notice that about:webrtc shows an increasing number of decoded frames, and very few dropped frames.
Updated•1 years ago
|
Comment 1•1 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::WebRTC' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•1 years ago
|
Comment 2•1 years ago
|
||
Set release status flags based on info from the regressing bug 1846796
Comment 3•1 years ago
|
||
Comment 4•1 years ago
|
||
https://pernos.co/debug/mcHmpQLC8KY97z1STlvytA/index.html#f{m[B+TV,DUw_,t[Ajs,Giuq_,f{e[B+TV,DSs_,s{af2nmYAAA,bAZI,uFNYACA,oFNcAXw___/ is a pernosco trace of this -- the offending code is commented out like the patch for release, but it allows inspecting the AVCC struct that's likely invalid.
Comment 5•1 years ago
|
||
Comment on attachment 9355594 [details]
Bug 1855636 - Disable part of 1846796 to unbreak some content on release and beta. r?#media-playback-reviewers
Beta/Release Uplift Approval Request
- User impact if declined: Some inbound h264 WebRTC video doesn't work anymore. This breaks content.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: repro URL is not public, ping @padenot (padenot@mozilla.com) for repro steps.
- List of other uplifts needed: none
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This is a low-risk beta / release-only patch while we figure out the real-fix for Nightly.
- String changes made/needed: none
- Is Android affected?: Yes
Updated•1 years ago
|
Comment 6•1 years ago
|
||
Comment on attachment 9355594 [details]
Bug 1855636 - Disable part of 1846796 to unbreak some content on release and beta. r?#media-playback-reviewers
Approved for 119.0b5
Updated•1 years ago
|
Updated•1 years ago
|
Updated•1 years ago
|
Updated•1 years ago
|
Comment 12•1 years ago
|
||
Hello,
Managed to reproduce this issue using the STR from the description with an affected build from 2023-09-28 , 120.0a1(20230928215127) with macOS 14.1.
Confirming this issue as verified fixed on 119.0b5(20231004091611) with macOS 14.1, Windows 11 and Ubuntu 22.
Comment 13•1 years ago
|
||
Comment on attachment 9355594 [details]
Bug 1855636 - Disable part of 1846796 to unbreak some content on release and beta. r?#media-playback-reviewers
Approved for our next 118 dot release, thanks.
Comment 14•1 years ago
|
||
uplift |
Comment 15•1 years ago
|
||
bugherder uplift |
Comment 16•1 years ago
|
||
Hello,
Confirming this issue as verified fixed on 118.0.2(20231009140911) using macOS 13, Windows 11 and Ubuntu 22.
Comment 17•1 year ago
|
||
The severity field is not set for this bug.
:mjf, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Comment 18•1 year ago
|
||
Clearing NI for Michael -- I handled this.
Updated•1 year ago
|
Comment 19•1 year ago
|
||
Can you land this on beta? We haven't done the "real" fix yet and we don't want to break this again.
Assignee | ||
Comment 20•1 year ago
•
|
||
Comment on attachment 9355594 [details]
Bug 1855636 - Disable part of 1846796 to unbreak some content on release and beta. r?#media-playback-reviewers
Hi dsmith, we need more time to fix this properly so D189507 has to be landed on beta again to avoid the problem
Beta/Release Uplift Approval Request
- User impact if declined: Some inbound h264 WebRTC video doesn't work anymore. This breaks content.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: repro URL is not public, ping @padenot (padenot@mozilla.com) for repro steps.
- List of other uplifts needed: none
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This is a low-risk beta / release-only patch while we figure out the real-fix for Nightly.
- String changes made/needed: none
- Is Android affected?: Yes
Comment 21•1 year ago
|
||
Approved for 120.0b3
... since this never made it to central during the 120 nightly cycle.
121 is still affected but we should prob disable it there too unless a fix is almost finished.
Updated•1 year ago
|
Comment 22•1 year ago
|
||
uplift |
Comment 23•1 year ago
|
||
Agreed - we should land this on m-c and move fixing and re-enabling to a new bug rather than having to remember to do this every cycle.
Comment 24•1 year ago
|
||
Chun-Min, can you handle this?
Assignee | ||
Comment 25•1 year ago
|
||
I'll revert the changes made in 1846796 first and work on a new fix.
Assignee | ||
Comment 26•1 year ago
|
||
This reverts commit 39e19ad141e661b878acaf3ed8c214dfd3fe2dae.
Assignee | ||
Comment 27•1 year ago
|
||
Depends on D192436
Assignee | ||
Comment 28•1 year ago
|
||
Depends on D192437
Assignee | ||
Comment 29•1 year ago
|
||
I've uploaded patches that revert the patches in bug 1846796
Comment 30•1 year ago
|
||
Comment 31•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8455d0b70dcd
https://hg.mozilla.org/mozilla-central/rev/e46ff3037f51
https://hg.mozilla.org/mozilla-central/rev/93b0e65b5ad2
Comment 32•1 year ago
|
||
Confirming this issue as verified fixed on 121.0a1(20231107214948) and 120.0b7(20231106091614) using macOS 14, Windows 11 and Ubuntu 22.
Description
•