Open Bug 1768038 Opened 2 years ago Updated 28 days ago

GMP (Widevine) crashes on Amazon Prime

Categories

(Core :: Audio/Video: GMP, defect, P3)

Firefox 85
defect

Tracking

()

Tracking Status
firefox-esr91 --- wontfix
firefox-esr102 --- wontfix
firefox-esr115 --- affected
firefox100 --- wontfix
firefox101 --- wontfix
firefox102 --- wontfix
firefox103 --- wontfix
firefox104 --- wontfix
firefox105 --- wontfix
firefox106 --- wontfix
firefox107 --- wontfix
firefox113 --- wontfix
firefox114 --- wontfix
firefox115 --- wontfix
firefox116 --- wontfix
firefox117 --- wontfix
firefox118 --- wontfix

People

(Reporter: cpeterson, Unassigned)

References

(Depends on 1 open bug, Regression)

Details

(Keywords: crash, regression, reproducible)

Attachments

(1 file)

STR:

  1. Open https://smile.amazon.com/gp/video/storefront. You don't need to be logged into an Amazon Prime account. I can repro this bug on Windows, but not macOS.
  2. Ctrl+click or middle mouse button click movie thumbnails to open 5-10 new tabs for the movie pages.
  3. Then press Ctrl+W to quickly close all the new tabs.

Result

After a few have been closed, I see the CDM crash infobar at the top of the page.

However, no crash shows up in about:crashes even if the submit option is chosen on the crash infobar. That is crash reporter bug 1765465.

I am able to reproduce this CDM crash in ESR 91 with Widevine version 4.10.2449.0 and Firefox 97-101 with Widevine version 4.10.2391.0 on Windows 11. I can't repro on macOS (version 11.6.4), so this might be a Windows-specific bug. I don't have a Linux box to test.

Notes:

  • I had to open and close a lot of tabs to get the crash.
  • I've reproed this on Win 10, and have heard this also happens on Win 11. Unless we get info to the contrary, my guess is this is not platform specific.
  • I'm still able to get other GMP crashes to show the same crash prompt, and they do appear in about:crashes. E.g. setting the media.gmp.plugin.crash pref to true while a Widevine GMP is active does seem to produce a report.

Removing the test signature here since it's unrelated.

Crash Signature: [@ mozilla::gmp::GMPChild::RecvCrashPluginNow ]

I can still reproduce this crash in 102 and 103, both 32 and 64-bit builds. I still get no crash reports (bug 1765465).

Hardware: Unspecified → All

I don't know why I didn't try this sooner: I used mozregression to bisect this crash to Nightly 85.0a1 build 2020-12-10. Unfortunately, I can't pinpoint the regressing changeset because we don't preserve autoland builds that old, but here is the regression range between 2020-12-09 and 2020-12-10:

https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7765d979d044be1fb03054013474a22e0b9ea022&tochange=7a6d6b986a1ed263db6d19ecbd56e2f4210870cf

I suspect this crash is a regression from bug 1675360, which changed how MediaKeys are initialized and shutdown.

Keywords: crash, regression
Regressed by: 1675360
Version: unspecified → Firefox 85
Flags: needinfo?(brycebugemail)

Set release status flags based on info from the regressing bug 1675360

Jim, is that really a P3/S3 given that we are crashing on a top streaming site?

Flags: needinfo?(jmathies)

(In reply to Pascal Chevrel:pascalc from comment #6)

Jim, is that really a P3/S3 given that we are crashing on a top streaming site?

This is a stress case when closing multiple tabs each with an amazon stream loaded in it. We have not been able to reproduce this in our testing.

Flags: needinfo?(jmathies)

Looks like it's too late for 107.
Leaving 108 status clear, unless anyone thinks we should be following this for a fix in 108?

I can still reproduce this CDM crash, but the STR no longer requires opening and then closing so many tabs. I see this crash when just opening 2 or 3 Amazon Prime tabs, sometimes without needing to close any of the tabs.

I'm using 32-bit Firefox Nightly 115 and Widevine Version: 4.10.2557.0 on Windows 11.

:jimm could this be triaged again based on comment 9? Maybe a recent change makes it easier to hit the problem?

Flags: needinfo?(jmathies)

Maybe QA could try and reproduce this bug?

Flags: qe-verify+

Andrew's been trying to find causes of this and harden up the code. We do get telemetry crash pings on these (we think).

(In reply to Chris Peterson [:cpeterson] from comment #9)

I can still reproduce this CDM crash, but the STR no longer requires opening and then closing so many tabs. I see this crash when just opening 2 or 3 Amazon Prime tabs, sometimes without needing to close any of the tabs.

I'm using 32-bit Firefox Nightly 115 and Widevine Version: 4.10.2557.0 on Windows 11.

So you open amazon video, play a movie and the plugin crashes immediately?

Flags: needinfo?(jmathies) → needinfo?(cpeterson)
Flags: needinfo?(jmathies)

(In reply to Jim Mathies [:jimm] from comment #12)

So you open amazon video, play a movie and the plugin crashes immediately?

You don't even need to play a movie, since Amazon queries the CDM before playing video. You don't need to be logged into an Amazon Prime account.

My simplified STR:

  1. Open https://www.amazon.com/gp/video/storefront in two or more tabs.
  2. Wait for the new tabs' loading spinners to finish loading. This is an important step!
  3. Close one of the new storefront tabs.

Result:

An infobar with the error "The WidevineCdm plugin has crashed." will be shown on any storefront tabs that are still open.

(Clicking the infobar's "Submit a crash report" button doesn't actually submit a crash report, but that's bug 1765465.)

Flags: needinfo?(cpeterson)
Depends on: gmp-load

Can you post your about support text, thanks!

Flags: needinfo?(jmathies) → needinfo?(cpeterson)
Attached file about-support.txt

I attached my about:support text.

Flags: needinfo?(cpeterson)
Keywords: reproducible

Just a reminder: I bisected this crash in comment 3 and I suspect it's a regression from bug 1675360, which changed how MediaKeys are initialized and shutdown.

Regression triage: about:support was added in comment 15.

Flags: needinfo?(jmathies)

I've run into the “The WidevineCdm plugin has crashed” info bar message. Tested on Windows 10, Windows 11 aarch64, Ubuntu 22 and macOS 12 with Firefox beta 119.0b9 and Firefox release 119.0 with new Widevine version 4.10.2710.0. Steps and the actual result are pretty similar with the ones provided in comment 13. Adding the pref media.gmp.plugin.crash=true while a Widevine GMP is active does seem to produce a crash report.

OS: Windows → All

This is a corner case we've done some work on reducing but we still see these occasionally. Good news: amazon tells us we have good error rates compared to other browsers.

Flags: needinfo?(jmathies)

It also crashes under Linux/x86_64 (Debian Firefox 125.0.3).

(In reply to Chris Peterson [:cpeterson] from comment #13)

(In reply to Jim Mathies [:jimm] from comment #12)

So you open amazon video, play a movie and the plugin crashes immediately?

You don't even need to play a movie, since Amazon queries the CDM before playing video. You don't need to be logged into an Amazon Prime account.

My simplified STR:

  1. Open https://www.amazon.com/gp/video/storefront in two or more tabs.
  2. Wait for the new tabs' loading spinners to finish loading. This is an important step!
  3. Close one of the new storefront tabs.

Result:

An infobar with the error "The WidevineCdm plugin has crashed." will be shown on any storefront tabs that are still open.

(Clicking the infobar's "Submit a crash report" button doesn't actually submit a crash report, but that's bug 1765465.)

Can't reproduce on 131.0b1 (64-bit), widevine 4.10.2710.0 on Windows 11.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: