Open Bug 1816229 Opened 2 years ago Updated 2 years ago

Crash in [@ std::vector<T>::size]

Categories

(Toolkit :: Crash Reporting, defect)

Unspecified
Windows 10
defect

Tracking

()

People

(Reporter: gsvelto, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/73e631c7-d7af-4024-9c42-61b3b0230207

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 10 frames of crashing thread:

0  xul.dll  std::vector<google_breakpad::ExceptionHandler*, std::allocator<google_breakpad::ExceptionHandler*> >::size const  /builds/worker/fetches/vs/VC/Tools/MSVC/14.16.27023/include/vector:1704
0  xul.dll  google_breakpad::AutoExceptionHandler::AutoExceptionHandler  toolkit/crashreporter/breakpad-client/windows/handler/exception_handler.cc:474
1  xul.dll  google_breakpad::ExceptionHandler::HandleException  toolkit/crashreporter/breakpad-client/windows/handler/exception_handler.cc:507
2  KERNELBASE.dll  UnhandledExceptionFilter  
3  ntdll.dll  RtlUserThreadStart$filt$0  
4  ntdll.dll  _C_specific_handler  
5  ntdll.dll  RtlpExecuteHandlerForException  
6  ntdll.dll  RtlDispatchException  
7  ntdll.dll  KiUserExceptionDispatch  
8  xul.dll  AnnotateMozCrashReason  mfbt/Assertions.h:40

This crash is occurring deep during shutdown: the shutdown hang terminator is trying to capture a minidump, which requires an auto-instanced Breakpad exception handler, but the shutdown procedure has already torn down the exception stack hence the crash. This is one of the many bugs that will be fixed by doing out-of-process crash reporting.

The severity field is not set for this bug.
:gsvelto, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(gsvelto)
Severity: -- → S3
Flags: needinfo?(gsvelto)
You need to log in before you can comment on or make changes to this bug.