1936558 - Crash in [@ nvd3dumx.dll | IsSupportedWMVDecodeGUID] on Windows 10 with media.ffvpx-hw.enabled

Status: RESOLVED WORKSFORME

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

Description

[Andrew McCreight [:mccr8]]

Crash report: https://crash-stats.mozilla.org/report/index/532dd8f8-7d8d-476d-90f6-a44120241210

Reason:

EXCEPTION_ACCESS_VIOLATION_READ

Top 9 frames:

0  nvd3dumx.dll  nvd3dumx.dll@0x18aa78
1  nvd3dumx.dll  nvd3dumx.dll@0x2307ff
2  d3d9.dll  IsSupportedWMVDecodeGUID
3  nvd3dumx.dll  nvd3dumx.dll@0x21a258
4  nvd3dumx.dll  nvd3dumx.dll@0x2e27a8
5  nvd3dumx.dll  nvd3dumx.dll@0x23196b
6  nvd3dumx.dll  nvd3dumx.dll@0x2ecc47
7  nvd3dumx.dll  nvd3dumx.dll@0x2ed3fe
8  nvd3dumx.dll  nvd3dumx.dll@0x230c40

The crash spike detector reported this as a Nightly crash spike, and in fact it does seem to have suddenly started happening there.

This is happening inside a Windows graphics driver without any real information about what is happening, but "IsSupportedWMVDecodeGUID" sounds like something related to media playback, and I know we have some new stuff there that might be going through Windows graphics drivers, so I'm filing this here. Looks like it is all Windows 10, from a variety of install times.

Comment 1

[Andrew McCreight [:mccr8]]

[Tracking Requested - why for this release]: Windows 10 crash regression.

Also of note, all of these are crashing on the CanvasRenderer thread. I'm not sure if that's consistent with my theory about this being a media playback problem.

Comment 2

[Gabriele Svelto [:gsvelto]]

We're getting to IsSupportedWMVDecodeGUID() only via stack-scanning. Let me see if I can find some better symbols for this so that we can get a properly unwinded stack.

Comment 3

[Andrew McCreight [:mccr8]]

This first appears in the 20241209143224 build. Nothing in the regression range looks too obviously related.

However, looking at the changes in the build one before that does include some changes that look related to hardware video decoding, in particular bug 1932772.

Comment 4

[Andrew McCreight [:mccr8]]

Ryan noted that it looked like the crashes went away, and bug 1936047 was filed as a regression from bug 1932772, so maybe this is a dupe of that?

Comment 5

[Andrew McCreight [:mccr8]]

Looks like this is set to be Nightly-only, and probably already fixed so clearing the tracking flag.

Comment 6

[Gabriele Svelto [:gsvelto]]

I managed to track down the driver and reprocessed the crashes with the unwinding information I could dig out of it. This is the new signature.

Comment 7

[Andrew McCreight [:mccr8]]

Thanks, that's a much better crash stack!

Comment 8

[Karl Tomlinson (:karlt)]

The fix for bug 1936047 disabled most of the changes for bug 1932772.

This will need be addressed for bug 1936128, so perhaps worth keeping open.

Comment 9

[Gabriele Svelto [:gsvelto]]

This reminded me that I should really overhaul the Windows graphics drivers' symbol scrapers.

Comment 10

[BugBot [:suhaib / :marco]]

:alwu, since you are the author of the regressor, bug 1932772, could you take a look?

For more information, please visit BugBot documentation.

Comment 11

[Alastor Wu [:alwu]]

Hasn't seen this crash in the past three months, I assume it has been fixed. Please feel free to reopen this bug if you see the same crash again.