This bug is for crash report bp-e73b841c-17b4-44d0-a5fc-4a10f0200318.

Top 10 frames of crashing thread:

0 vcruntime140.dll memcpy f:\dd\vctools\crt\vcruntime\src\string\i386\memcpy.asm:657
1 xul.dll mozilla::ipc::CrashReporterClient::AnnotateCrashReport ipc/glue/CrashReporterClient.cpp:29
2 xul.dll CrashReporter::AnnotateCrashReport toolkit/crashreporter/nsExceptionHandler.cpp:2407
3 xul.dll mozilla::dom::ContentChild::ShutdownInternal dom/ipc/ContentChild.cpp:2947
4 xul.dll mozilla::dom::ContentChild::RecvShutdown dom/ipc/ContentChild.cpp:2878
5 xul.dll mozilla::dom::PContentChild::OnMessageReceived ipc/ipdl/PContentChild.cpp:11165
6 xul.dll mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2111
7 xul.dll mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1990
8 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1220
9 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:481

It looks like these are being called from mozilla::dom::ContentChild::ShutdownInternal().

Setting annotations in child processes is remarkably slow and involves shared memory so it's possible we get stuck doing it while shutting down. Bug 1614933 is removing that stuff and making content process annotations much faster so I expect this to go away as soon as I land that.

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

For more information, please visit auto_nag documentation.

P4 because this is likely going to go away after bug 1614933 lands.

I forgot about this... it was fixed by bug 1614933.