搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Widevine crashes every time I visit Netflix or Amazon

more options

I'm on Arch Linux and recently updated Firefox to version 73.0 through pacman. I got no errors and Firefox works fine. Except that Widevine crashes whenever I visit Netflix or Amazon. I tried removing the plugin and reinstalling it, reinstalling Firefox and starting Firefox in safe mode. If anyone knows a solution to my problem your help would be much appreciated!

被選擇的解決方法

So I now downgraded glibc and lib32-glibc which fixed the problem. Thank you all for your help! Have a lovely day :)

從原來的回覆中察看解決方案 👍 0

所有回覆 (10)

more options

It looks like you're actually on Firefox 74 which is not a stable release. Maybe you should try rolling it back to the current stable release.

Other than that, you can try to remove video hardware acceleration by disabling media.hardware-video-decoding.enabled in about:config.

more options

Hey. Thank you for your reply. I posted that question from the firefox developer edition as I wanted to see if it worked there, but it didn't either. I tried disabling hardware video decoding but it sadly didn't work either. Thank you for your help though.

more options

Does Widevine work here ?

more options

cor-el said

Does Widevine work here ?

Sadly it still crashes immediately

more options

Hi Quirinbrunner:

I believe this is fixed in Firefox 73.0.1 which was released today. Please give it a try.

Cheers!

...Roland

more options

Sadly it still crashes :/

more options

Is there any information I could give that could help?

more options

選擇的解決方法

So I now downgraded glibc and lib32-glibc which fixed the problem. Thank you all for your help! Have a lovely day :)

more options

If anyone is running into this and is willing to test, it would be useful to know if running with the environment variable `MOZ_DISABLE_GMP_SANDBOX=1` set impacts the crash. That env var can be used to disable the sandbox Widevine runs in. You can unset the var once you've tested.

We've seen new versions of glibc run into the sandbox because they change the syscalls some functions use. So if setting that fixes the problem, that would be helpful to know. If it does fix the problem, running with the env var `MOZ_SANDBOX_LOGGING=1` set should log to the terminal what call is blocked. If Mozilla can get that info we can use it to adjust the sandbox as needed.

more options

bvandyk said

If anyone is running into this and is willing to test, it would be useful to know if running with the environment variable `MOZ_DISABLE_GMP_SANDBOX=1` set impacts the crash. That env var can be used to disable the sandbox Widevine runs in. You can unset the var once you've tested. We've seen new versions of glibc run into the sandbox because they change the syscalls some functions use. So if setting that fixes the problem, that would be helpful to know. If it does fix the problem, running with the env var `MOZ_SANDBOX_LOGGING=1` set should log to the terminal what call is blocked. If Mozilla can get that info we can use it to adjust the sandbox as needed.

I would love to help but even with the glib and lib32-versions at the versions they were before it doesn't crash anymore.