Inuyasha preview on Netflix causes every Firefox window to flash and go blank.
Categories
(Core :: Graphics: WebRender, defect, P3)
Tracking
()
People
(Reporter: cmartin, Assigned: gw)
References
(Regression)
Details
(Keywords: regression)
Crash Data
Attachments
(7 files, 2 obsolete files)
45.63 KB,
text/plain
|
Details | |
2.36 MB,
text/plain
|
Details | |
48 bytes,
text/x-phabricator-request
|
diannaS
:
approval-mozilla-release+
|
Details | Review |
1008.65 KB,
image/png
|
Details | |
451.98 KB,
image/png
|
Details | |
1.08 MB,
video/mp4
|
Details | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr115+
|
Details | Review |
This report comes from my sister, but I was able to reproduce on my own machine quite easily. Here are the steps:
- Open up a bunch of Firefox windows. Doesn't seem to matter if they're private or not, and they can be on multiple monitors.
- Navigate to netflix.com in one of them and search for "Inuyasha".
- Click on the Inuyasha icon to cause the preview to launch.
- Notice that all your Firefox windows have flashed and then gone blank (it seems you can click in them to bring their contents back).
Note that, for some reason, it is specifically Inuyasha that reproduces this issue -- Both my sister and I were unable to find another Netflix preview that caused this same issue.
Note that non-Firefox windows are not affected.
Comment 1•11 months ago
|
||
This looks like a GPU process crash — or, at least, the behavior is strikingly similar to what happens if I just kill the GPU process. Are there any crashes listed in about:crashes
?
Can you reproduce this during a profiler run while using the Graphics preset on about:profiling
?
(I don't have a Netflix account, so I can't easily perform the test as written.)
Comment 2•11 months ago
|
||
Comment 3•11 months ago
|
||
Updated•11 months ago
|
Comment 4•11 months ago
|
||
This is the regression range I got :
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=1995198e0bee1b9f7d4ac3a5286fb89a8305fa28&tochange=925231a8fb5eccf055afb3e9921596d8f990128b
which seems to imply bug 1859432
Comment 5•11 months ago
|
||
Comment 6•11 months ago
|
||
Set release status flags based on info from the regressing bug 1859432
Comment 7•11 months ago
|
||
"Inuyasha" did not exist in Netflix in Japan. But I could reproduce the problem with a content of Bug 1705940.
Comment 8•11 months ago
•
|
||
From the followings, i am going to create a new bug for fixing the problem.
- "Inuyasha" did not exist in Netflix in Japan
- Netflix video playback with local build does not work. It causes playback error.(Bug 1763811 )
Comment 9•11 months ago
•
|
||
On Windows, 10-bit VP9 video caused the problem when video was decoded by software decoder.
And before Bug 1859432 fix, the video should cause the problem when GPU process did not exist. See esr crash
And on Linux, 10-bit VP9 video with software decoder did not cause the problem.
Implementation of batch_upload seems to have a problem.
When } else if use_batch_upload { part is disabled with local build, the video was played back without problem.
Comment 10•11 months ago
|
||
From comment 9, it might be better to fix WebRender batch upload.
:gw, can you comment to it?
Updated•11 months ago
|
Assignee | ||
Updated•11 months ago
|
Assignee | ||
Comment 11•11 months ago
|
||
Comment 13•11 months ago
|
||
Comment 14•11 months ago
|
||
bugherder |
Reporter | ||
Updated•11 months ago
|
Comment 15•11 months ago
|
||
This is fixed on latest Nightly for me. Thanks!
Comment 16•11 months ago
|
||
The patch landed in nightly and beta is affected.
:gw, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox124
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Comment 17•11 months ago
|
||
Sotaro, do you think this is important to uplift to beta?
Comment 18•11 months ago
|
||
FYI there are no more betas so it would have to be important enough to uplift to an RC respin (if there is one) or a planned dot release.
Comment 19•11 months ago
|
||
(In reply to Glenn Watson [:gw] from comment #17)
Sotaro, do you think this is important to uplift to beta?
The number of crashes are not high. But the crash happens with the specific STR of Netflix. Then I think it is important enough to uplift.
:jrmuizel, how do you think?
Assignee | ||
Comment 20•11 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D203973
Updated•11 months ago
|
Comment 21•11 months ago
|
||
Uplift Approval Request
- Steps to reproduce for manual QE testing: Per bug report
- User impact if declined: GPU process crashes on some video on popular sites such as Netflix
- Fix verified in Nightly: yes
- Is Android affected?: yes
- String changes made/needed: None
- Needs manual QE test: yes
- Explanation of risk level: Minor patch, has been in nightly for a while
- Code covered by automated testing: no
- Risk associated with taking this patch: Low
Updated•11 months ago
|
Comment 22•11 months ago
•
|
||
I tried reproducing the issue with Firefox 124.0RC1 and Firefox 125.0a1 (2024-03-06) on two different Windows 10x64 machines by following the steps from comment 0 but without any luck. I have also tried the steps on an affected build on macOS 12 and Ubuntu 23.10 but the issue could no be reproduced. Just to be safe I have also verified that the issue is not reproducing with Firefox 125.0a1 (2024-03-12) on Windows 10x64 and macOS 12 by hovering over the Inuyasha
title or playing it. Note that a US VPN was used to see the Inuyasha
Netflix title since it seems that is not available in Romania.
Could one of you confirm whether the problem has been resolved by using the most recent nightly build? Thank you in advance!
Comment 23•11 months ago
|
||
(In reply to Alexandru Trif, Desktop QA [:atrif] from comment #22)
I tried reproducing the issue with Firefox 124.0RC1 and Firefox 125.0a1 (2024-03-06) on two different Windows 10x64 machines by following the steps from comment 0 but without any luck. I have also tried the steps on an affected build on macOS 12 and Ubuntu 23.10 but the issue could no be reproduced. Just to be safe I have also verified that the issue is not reproducing with Firefox 125.0a1 (2024-03-12) on Windows 10x64 and macOS 12 by hovering over the
Inuyasha
title or playing it. Note that a US VPN was used to see theInuyasha
Netflix title since it seems that is not available in Romania.Could one of you confirm whether the problem has been resolved by using the most recent nightly build? Thank you in advance!
I confirmed fixed on Nightly in comment #15.
Comment 24•11 months ago
|
||
Oh sorry, I somehow missed that comment. Setting this as verified for Firefox 125 based on comment 15 and dropping the qe+ flag since we could not reproduce the issue. Thank you!
Comment 25•11 months ago
|
||
Chris, can you post a screen shot of the issue? The video won't play for me.
Reporter | ||
Comment 26•11 months ago
•
|
||
I have attached a screenshot of what Netflix looks like immediately before it tries to play the preview
Reporter | ||
Comment 27•11 months ago
|
||
And then this is what happens when FF tries to draw the first frame of the preview.
Reporter | ||
Comment 28•11 months ago
|
||
Bob Hood - I was also not able to play it back for some reason through Firefox, even though it plays fine using VLC Media Player on my machine.
I re-uploaded it after running it through FFMpeg to clean up the file format. Seems to work now.
Updated•10 months ago
|
Comment 29•10 months ago
|
||
Comment on attachment 9390672 [details]
Bug 1883932 - Add R16 support to texture upload pool
requesting NI for the conflict on the release patch
Updated•10 months ago
|
Comment 30•10 months ago
|
||
uplift |
Updated•10 months ago
|
Comment 31•10 months ago
|
||
Comment on attachment 9390055 [details]
Bug 1883932 - Add R16 support to texture upload pool
Approved for 124.0.2 dot release
Updated•10 months ago
|
Assignee | ||
Comment 32•10 months ago
|
||
Dianna has resolved the conflict in this patch.
Comment 33•10 months ago
|
||
Hello! Would one of you mind trying again with Firefox 124.0.2 to see if the issue is fixed? Thank you both in advance!
Comment 34•10 months ago
|
||
Glenn, should we consider uplifting this to ESR as well?
Assignee | ||
Comment 35•10 months ago
|
||
Yes, probably worth doing. Dianna, do you need a new request made for that?
Comment 36•10 months ago
•
|
||
Yes it would need a new uplift request for esr (prob a rebased patch)
(Marking esr as affected based on comment 9)
Reporter | ||
Comment 37•10 months ago
|
||
(In reply to Alexandru Trif, Desktop QA [:atrif] from comment #33)
Hello! Would one of you mind trying again with Firefox 124.0.2 to see if the issue is fixed? Thank you both in advance!
I can confirm that the bug is fixed in 124.0.2.
Updated•10 months ago
|
Assignee | ||
Comment 38•10 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D203973
Updated•10 months ago
|
Comment 39•10 months ago
|
||
esr115 Uplift Approval Request
- User impact if declined: Crashes on certain video formats on Netflix etc
- Code covered by automated testing: no
- Fix verified in Nightly: yes
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: Per bug report
- Risk associated with taking this patch: Low
- Explanation of risk level: Has been in nightly and release for a while
- String changes made/needed: None
- Is Android affected?: yes
Assignee | ||
Comment 40•10 months ago
|
||
Added a patch rebased on esr115 branch and requested uplift.
Updated•10 months ago
|
Comment 41•10 months ago
|
||
uplift |
Updated•10 months ago
|
Comment 42•10 months ago
|
||
Hello! Could you also please verify the fix on Firefox ESR 115.10? Thank you!
Updated•10 months ago
|
Reporter | ||
Comment 43•10 months ago
|
||
Confirmed. The fix works on ESR 115.10.
Description
•