DRM Content not playing with WideVineCDM 4.10.2557.0 in Firefox 108.0.1
Categories
(Core :: Audio/Video: GMP, defect)
Tracking
()
People
(Reporter: anubhavsachan4shree, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(6 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0
Steps to reproduce:
Open any DRM Content providing website such as Hotstar, Prime Video, Netflix, Spotify
Actual results:
Error comes as "The WidevineCdm plugin has crashed. Reload Page or Submit a bug"
Expected results:
Video/Audio must have been playing.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 2•2 years ago
|
||
If you are using an ARM based Windows laptop running Windows 10, we know of an issue with this type of setup and DRM playback. Upgrading to Windows 11 should address it. We're hopeful the same fix that's in Windows 11 will eventually get ported to Windows 10 by Microsoft. Currently though aside from the upgrade path we don't have a work around.
Can you confirm your setup matches this for us?
Comment 3•2 years ago
|
||
Removing confidentiality so this information is more public.
Updated•2 years ago
|
(In reply to Jim Mathies [:jimm] from comment #2)
If you are using an ARM based Windows laptop running Windows 10, we know of an issue with this type of setup and DRM playback. Upgrading to Windows 11 should address it. We're hopeful the same fix that's in Windows 11 will eventually get ported to Windows 10 by Microsoft. Currently though aside from the upgrade path we don't have a work around.
Can you confirm your setup matches this for us?
No it is not an ARM-based processor.
I'm running Windows 11 Home Single Language 22H2 22621.963 on a 12th Gen Intel(R) Core(TM) i7-1260P Processor with 16GB RAM.
I'm unable to view: https://bugzilla.mozilla.org/show_bug.cgi?id=1804882.
Can you please provide access?
Updated•2 years ago
|
Comment 6•2 years ago
|
||
(In reply to anubhav from comment #5)
I'm unable to view: https://bugzilla.mozilla.org/show_bug.cgi?id=1804882.
Can you please provide access?
Have you tried restarting the browser? We have no reports of issues with the new cdm (2557) and playback other than with Windows ARM devices. Also, can you post your about:support info? Thanks!
Comment 7•2 years ago
|
||
Also, do you see any crash reports in about:crashes?
(In reply to Jim Mathies [:jimm] from comment #6)
(In reply to anubhav from comment #5)
I'm unable to view: https://bugzilla.mozilla.org/show_bug.cgi?id=1804882.
Can you please provide access?
Have you tried restarting the browser? We have no reports of issues with the new cdm (2557) and playback other than with Windows ARM devices. Also, can you post your about:support info? Thanks!
Yes, tried restarting browser, but no fix.
Reporter | ||
Comment 10•2 years ago
|
||
(In reply to Jim Mathies [:jimm] from comment #7)
Also, do you see any crash reports in about:crashes?
No crash reports have been submitted.
Comment 11•2 years ago
|
||
I tried reproducing this issue on Windows 11 21H2(OS Build 22000.1335) but I was unsuccesful. I tested on Spotify, Netflix and Primevideo. No crashes and no errors in the Browser Console.
Reporter, could you please try running Firefox in Troubleshoot Mode(: https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode#w_how-to-start-firefox-in-troubleshoot-mode) and see if you get any crashes?
Reporter | ||
Comment 12•2 years ago
|
||
My Windows is Win 11 22H2 22621.963
I tried running Firefox in Troubleshoot Mode, and still see crashes.
Attaching those files.
Reporter | ||
Comment 13•2 years ago
|
||
Reporter | ||
Comment 14•2 years ago
|
||
Updated•2 years ago
|
Comment 15•2 years ago
|
||
Could you try the same sites in Chrome to see if you have the same issue? They use the same widevine cdm as we do.
Reporter | ||
Comment 16•2 years ago
|
||
(In reply to Jim Mathies [:jimm] from comment #15)
Could you try the same sites in Chrome to see if you have the same issue? They use the same widevine cdm as we do.
Yes, it's working fine. I've also tried on Microsoft Edge [Version 108.0.1462.54 (Official build) (64-bit)].
Everything is working as usual.
Updated•2 years ago
|
Comment 18•2 years ago
|
||
(In reply to anubhav from comment #17)
Any update?
Hey sorry. So if you have a sec, maybe you could try to capture some logs that would help diagnose what's going wrong. The steps are as follows -
- Open a command console and browse to your install location for Firefox.
- enter 'set MOZ_DISABLE_GMP_SANDBOX=1'
- Launch Firefox from the command console (firefox.exe (return))
- In the browser, open a tab and visit about:logging
- Enter 'GMP:5,EME:5' in the 'new log modules' text edit and click on 'Set Log Modules'
- Under Output choose 'Logging to a file' and choose a suitable temp path and then click 'Set Log File'.
- In a new tab visit the test Widevine site (http://shaka-player-demo.appspot.com/) or streaming provider like Netflix.
In the temp dir, you should get two logs (something like 'emelog.txt-child.23884.moz_log' and 'emelog.txt-main.23435.moz_log'). Attach those to this bug so we can take a look.
Reporter | ||
Comment 19•2 years ago
|
||
Added logs as per your request
Reporter | ||
Comment 20•2 years ago
|
||
Screenshot showing DRM Content is not available.
Reporter | ||
Comment 22•2 years ago
|
||
Still no update?
Comment 23•2 years ago
|
||
(In reply to anubhav from comment #22)
Still no update?
Hello, we've been making progress on this in nightly. It should hopefully be working now. Can you test in the latest nightly build? Thanks!
Comment 24•2 years ago
|
||
Oh wait, this is not an ARM laptop, sorry, my mistake. I'll try to investigate.
Reporter | ||
Comment 25•2 years ago
|
||
Are you guys able to reproduce the issue?
Comment 26•2 years ago
|
||
(In reply to Andrew Osmond [:aosmond] (he/him) from comment #23)
(In reply to anubhav from comment #22)
Still no update?
Hello, we've been making progress on this in nightly. It should hopefully be working now. Can you test in the latest nightly build? Thanks!
Hi, I had the same issue (Asus NovaGo TP370QL, Windows 10 22H2, Firefox 110.0.1 arm64) and latest Nightly appears to be working for me.
Reporter | ||
Comment 27•2 years ago
|
||
(In reply to drake127 from comment #26)
(In reply to Andrew Osmond [:aosmond] (he/him) from comment #23)
(In reply to anubhav from comment #22)
Still no update?
Hello, we've been making progress on this in nightly. It should hopefully be working now. Can you test in the latest nightly build? Thanks!
Hi, I had the same issue (Asus NovaGo TP370QL, Windows 10 22H2, Firefox 110.0.1 arm64) and latest Nightly appears to be working for me.
Hi, yes, as informed by Andrew, the issue is solved for arm64 in nightly, but I have an amd64 machine.
Can you tell me which WideVineCDM version is being used in Nightly 110.0.1 arm64?
Comment 28•2 years ago
|
||
(In reply to anubhav from comment #27)
Can you tell me which WideVineCDM version is being used in Nightly 110.0.1 arm64?
I see 4.10.2557.0 (folder name in gmp-widevinecdm).
Reporter | ||
Comment 29•2 years ago
|
||
(In reply to drake127 from comment #28)
I see 4.10.2557.0 (folder name in gmp-widevinecdm).
Interesting. Till this point, I was thinking v4.10.2557.0 was causing issue in my machine (Win 11 22H2 with Intel i7 12th Gen).
However, on checking with Chrome/Edge, they are also using same version of WideVineCDM i.e.4.10.2557.0 where everything is running smoothly.
@jmathies, @aosmond
This means the issue between Firefox RAM Management probably. As far as I can understand, once the DRM content is loaded, it consumes a lot of power for a moment, and then Firefox kills the Widevine Plugin to save power.
I can assure that I have run Firefox in maximum performance settings as well. But no luck.
Comment 30•2 years ago
|
||
This ultimately is probably a dupe of the crashes we are trying to figure out in bug 1444334. If you aren't getting crash reports generated, it is possible the issue is more prevalent than we realize. Hopefully we will be able to get more diagnostics out of this with the patches I've been landing.
Comment 31•2 years ago
|
||
I came to that conclusion based on the logs -- the launching process fails on SendStartPlugin. The crashes in bug 1444334 are the other side of that.
Updated•2 years ago
|
Description
•