Open Bug 1864990 Opened 1 year ago Updated 1 year ago

Crash in [@ nsQueryInterfaceISupports::operator()]

Categories

(Core :: XPCOM, defect)

x86
All
defect

Tracking

()

Tracking Status
firefox121 --- affected

People

(Reporter: release-mgmt-account-bot, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/ee218a82-9cff-4b1a-a1e7-5c0f40231110

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames of crashing thread:

0  ?  @0x00007f01a7ff3090  
1  libxul.so  nsQueryInterfaceISupports::operator const  xpcom/base/nsCOMPtr.cpp:13
1  libxul.so  nsQueryInterface<nsIRunnable>::operator const  xpcom/base/nsCOMPtr.h:165
1  libxul.so  nsCOMPtr<nsINamed>::assign_from_qi<nsIRunnable>  xpcom/base/nsCOMPtr.h:827
1  libxul.so  nsCOMPtr<nsINamed>::nsCOMPtr<nsIRunnable>  xpcom/base/nsCOMPtr.h:482
1  libxul.so  mozilla::RunnableTask::GetName  xpcom/threads/TaskController.cpp:563
1  libxul.so  mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal  xpcom/threads/TaskController.cpp:863
2  libxul.so  mozilla::TaskController::ExecuteNextTaskOnlyMainThreadInternal  xpcom/threads/TaskController.cpp:699
2  libxul.so  mozilla::TaskController::ProcessPendingMTTask  xpcom/threads/TaskController.cpp:485
2  libxul.so  mozilla::TaskController::TaskController const  xpcom/threads/TaskController.cpp:211

By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:

  • First crash report: 2023-10-10
  • Process type: Multiple distinct types
  • Is startup crash: No
  • Has user comments: No
  • Is null crash: Yes - 3 out of 8 crashes happened on null or near null memory address

This is very likely caused by flaky hardware, several bit-flips were detected and the remaining addresses are all over the place.

Component: General → XPCOM
Severity: -- → S4
You need to log in before you can comment on or make changes to this bug.