Closed Bug 1715297 Opened 3 years ago Closed 2 years ago

Crash in [@ CStdMarshal::ReleaseAllServerIPIDEntries]

Categories

(Core :: Disability Access APIs, defect)

Unspecified
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: gsvelto, Unassigned)

References

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/58683925-ff78-4eac-a6b4-bfe720210605

Reason: EXCEPTION_ACCESS_VIOLATION_WRITE

Top 10 frames of crashing thread:

0 combase.dll CStdMarshal::ReleaseAllServerIPIDEntries onecore\com\combase\dcomrem\marshal.cxx:8016
1 combase.dll CStdIdentity::CInternalUnk::Release onecore\com\combase\dcomrem\stdid.cxx:945
2 xul.dll mozilla::mscom::detail::InternalUnknown<mozilla::mscom::FastMarshaler>::Release ipc/mscom/Aggregation.h:55
3 xul.dll mozilla::mscom::Interceptor::~Interceptor ipc/mscom/Interceptor.cpp:262
4 xul.dll mozilla::mscom::Interceptor::~Interceptor ipc/mscom/Interceptor.cpp:247
5 xul.dll mozilla::mscom::WeakReferenceSupport::Release ipc/mscom/WeakRef.cpp:150
6 xul.dll detail::ProxyReleaseEvent<mozilla::mscom::WeakReferenceSupport>::Run xpcom/threads/nsProxyRelease.h:37
7 xul.dll mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal xpcom/threads/TaskController.cpp:786
8 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1159
9 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:85

Unsure what's going on here besides the fact that we're accessing a NULL pointer.

Severity: -- → S2

Looks similar to bug 1664224.

See Also: → 1664224
Depends on: 1737193

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Severity: S2 → S3

Whatever this was it's gone, remaining crash reports are from older builds.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.