Crash in [@ CGuidStr::{ctor}] from mozilla::MFTDecoder::Create()
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox128 | --- | affected |
People
(Reporter: release-mgmt-account-bot, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/ec5e3841-73f1-43b3-b83b-063a90240531
Reason: EXCEPTION_STACK_BUFFER_OVERRUN / FAST_FAIL_GUARD_ICALL_CHECK_FAILURE
Top 10 frames of crashing thread:
0 ntdll.dll RtlFailFast2
1 ntdll.dll RtlpHandleInvalidUserCallTarget
2 ntdll.dll LdrpHandleInvalidUserCallTarget
3 combase.dll CGuidStr::{ctor} onecore\com\combase\objact\dllcache.cxx:2580
3 combase.dll CClassCache::CDllPathEntry::DllGetClassObject onecore\com\combase\objact\dllcache.cxx:3249
4 combase.dll CClassCache::CDllFnPtrMoniker::BindToObject onecore\com\combase\ih\tls.h:401
5 combase.dll CGuidStr::{ctor} onecore\com\combase\objact\dllcache.cxx:5053
5 combase.dll ICoCreateInstanceEx onecore\com\combase\objact\objact.cxx:1865
6 combase.dll CComActivator::DoCreateInstance onecore\com\combase\objact\immact.hxx:392
7 combase.dll CoCreateInstanceEx onecore\com\combase\objact\actapi.cxx:177
By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:
- First crash report: 2024-05-17
- Process type: GPU
- Is startup crash: No
- Has user comments: No
- Is null crash: No
Comment 1•8 months ago
|
||
All 7 recent crashes have mozilla::MFTDecoder::Create() in the stack, so I'm moving it to A/V: Playback.
Comment 2•7 months ago
|
||
Happening in
mozilla::MFTDecoder::Create(_GUID const&, _GUID const&, _GUID const&)
In the gpu process. Low volume at this point, but appears to be picking up.
Comment 3•6 months ago
|
||
I just stumbled upon this while doing nightly crash triage. Here's a couple of observations:
- This only seems to affect the most recent versions of Windows 10. We've got the vast majority of crashes on version 10.0.19045 and just a handful on 10.0.19044
- Several crashes - but not all - have the last error set to
ERROR_SXS_KEY_NOT_FOUND
which may indicate that we might be entering some error-handling path within Microsoft code which then triggers the crash
Comment 4•8 days ago
|
||
Crash observed here when I opened the two links of the first message in this Slack thread - https://www.windows93.net/ and https://justforfun.io/ - and move on to open the link in the first reply - https://tixy.land/ . There was slowness or hang of the application for a short time, and afterwards the (pinned) Slack tab had been closed without my request.
Description
•