Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

The WidevineCDM plugin has crashed. (on Windows 10)

  • 3 ответа
  • 1 имеет эту проблему
  • 817 просмотров
  • Последний ответ от slo_bern

more options

This is suddenly happening to me on Firefox 92.0 (64-bit) running on Windows 10 21H1. Worked on 9/12, failed consistently starting 9/13, (possibly coinciding with auto-update from FF 91.0.2 to FF 92.0). I'm using WidevineCDM version 4.10.2209.1 to watch Xfinity stream recordings. Have submitted 3 crash reports via FF.

This is suddenly happening to me on Firefox 92.0 (64-bit) running on Windows 10 21H1. Worked on 9/12, failed consistently starting 9/13, (possibly coinciding with auto-update from FF 91.0.2 to FF 92.0). I'm using WidevineCDM version 4.10.2209.1 to watch Xfinity stream recordings. Have submitted 3 crash reports via FF.

Выбранное решение

BTW, It seems I have resolved it on my own, by using a couple of the buttons on the about:support page...

First I cleared the startup cache, restarted FF, and then I Refreshed Firefox.

Hope this helps.

Прочитайте этот ответ в контексте 👍 0

Все ответы (3)

more options

If you have submitted crash reports, please post the IDs of one or more recent crash reports that start with "bp-".

  • bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

You can find the report ID of recent crash reports on the "Help -> More Troubleshooting Information" (about:support) page.

  • click the "All Crash Reports" button on this page to open the about:crashes page and see all crash reports.

Alternatively you can open about:crashes via the location/address bar.

See also:

more options

Apparently some of the submissions failed. Here are a couple that were submitted:

bp-e0c2aeb6-4af5-4f78-bb05-383460210914 bp-6490b038-0de9-4f8c-846c-4b4e20210914

more options

Выбранное решение

BTW, It seems I have resolved it on my own, by using a couple of the buttons on the about:support page...

First I cleared the startup cache, restarted FF, and then I Refreshed Firefox.

Hope this helps.