X
點擊此處開啟此網站的行動版。

技術支援討論區

Widevine crashes every time I visit Netflix or Amazon

已張貼

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!

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
引用

額外的系統細節

已安裝的外掛程式

  • Shockwave Flash 32.0 r0

應用程式

  • User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0

更多資訊

Matthew Thomas
  • Top 25 Contributor
13 個解決方法 90 個答案

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.

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.
這篇文章有幫助嗎?
引用

提出問題者

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.

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.
這篇文章有幫助嗎?
引用
cor-el
  • Top 10 Contributor
  • Moderator
17865 個解決方法 161655 個答案

Does Widevine work here ?

Does Widevine work here ? *https://shaka-player-demo.appspot.com/demo/
這篇文章有幫助嗎?
引用

提出問題者

cor-el said

Does Widevine work here ?

Sadly it still crashes immediately

''cor-el [[#answer-1290430|said]]'' <blockquote> Does Widevine work here ? *https://shaka-player-demo.appspot.com/demo/ </blockquote> Sadly it still crashes immediately
這篇文章有幫助嗎?
引用
Roland Tanglao
  • Administrator
77 個解決方法 848 個答案

Hi Quirinbrunner:

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

Cheers!

...Roland

Hi Quirinbrunner: I believe this is fixed in Firefox 73.0.1 which was released today. Please give it a try. Cheers! ...Roland
這篇文章有幫助嗎?
引用

提出問題者

Sadly it still crashes :/

Sadly it still crashes :/
這篇文章有幫助嗎?
引用

提出問題者

Is there any information I could give that could help?

Is there any information I could give that could help?
這篇文章有幫助嗎?
引用

選擇的解決方法

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

So I now downgraded glibc and lib32-glibc which fixed the problem. Thank you all for your help! Have a lovely day :)
這篇文章有幫助嗎?
引用
bvandyk 0 個解決方法 1 個答案

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.

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.
這篇文章有幫助嗎?
引用

提出問題者

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.

''bvandyk [[#answer-1291527|said]]'' <blockquote> 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. </blockquote> I would love to help but even with the glib and lib32-versions at the versions they were before it doesn't crash anymore.
這篇文章有幫助嗎?
引用
問個問題

如果您還沒有帳號,您必須先 登入您的帳號 來回覆文章。請 開始一個新問題