Crash in [@ msmpeg2vdec.dll | ippiFilterDeblockingLuma_HorEdge_H264_8u_C1IR] on family 6 model 183 stepping 1
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
People
(Reporter: mccr8, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/ac0f5469-5c90-4de1-bcda-588880250630
Reason:
EXCEPTION_STACK_BUFFER_OVERRUN / FAST_FAIL_STACK_COOKIE_CHECK_FAILURE
Top 5 frames:
0 msmpeg2vdec.dll msmpeg2vdec.dll@0x624bd
1 mfperfhelper.dll ippiFilterDeblockingLuma_HorEdge_H264_8u_C1IR
2 msmpeg2vdec.dll msmpeg2vdec.dll@0x112bd5
3 msmpeg2vdec.dll msmpeg2vdec.dll@0x119c42
4 ntdll.dll EtwEventWrite
This was reported via the crash spike reporter. 55 crashes in the last week which is quite a few. These are all EXCEPTION_STACK_BUFFER_OVERRUN / FAST_FAIL_STACK_COOKIE_CHECK_FAILURE
. Looking at a few of these reports, I'm struck by what looks like a colossal number of identical threads, hundreds in some cases. These threads have a few frames of unknown in nvwgf2umx.dll
and not much else. It almost looks like we are leaking threads. Maybe that could cause us to run out of memory for stacks or something? Seems weird and bad in any case.
This sounds like it is related to media playback using Windows drivers so I'm filing this in playback but maybe that's not right.
Comment 1•4 months ago
|
||
100% crashes from family 6 model 183 stepping 1
It's our good friend Raptor Lake who's at it again.
Reporter | ||
Comment 2•4 months ago
|
||
Good catch. Somehow I didn't think to check for that with what looked like a resource exhaustion issue and not a simple crash.
Comment 3•4 months ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 desktop browser crashes on nightly
For more information, please visit BugBot documentation.
Updated•3 months ago
|
![]() |
||
Updated•3 months ago
|
Comment 4•3 months ago
|
||
Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.
For more information, please visit BugBot documentation.
Description
•