1579800 - Crash in [@ mozilla::ipc::CrashReporterClient::InitSingleton<T>]

Status: RESOLVED WORKSFORME

(Toolkit :: Crash Reporting, defect, P3)

Description

[Gabriele Svelto [:gsvelto] (PTO)]

This bug is for crash report bp-4e06d931-55b5-489f-87b7-4a46a0190908.

Top 10 frames of crashing thread:

0 xul.dll static void mozilla::ipc::CrashReporterClient::InitSingleton<mozilla::net::SocketProcessChild> ipc/glue/CrashReporterClient.h:42
1 xul.dll bool mozilla::net::SocketProcessChild::Init netwerk/ipc/SocketProcessChild.cpp:82
2 xul.dll bool mozilla::net::SocketProcessImpl::Init netwerk/ipc/SocketProcessImpl.cpp:84
3 xul.dll XRE_InitChildProcess toolkit/xre/nsEmbedFunctions.cpp:739
4 firefox.exe static int content_process_main ipc/contentproc/plugin-container.cpp:56
5 firefox.exe static int NS_internal_main browser/app/nsBrowserApp.cpp:272
6 firefox.exe wmain toolkit/xre/nsWindowsWMain.cpp:131
7 firefox.exe static int __scrt_common_main_seh f:/dd/vctools/crt/vcstartup/src/startup/exe_common.inl:288
8 kernel32.dll BaseThreadInitThunk 
9 ntdll.dll RtlUserThreadStart 

The first crashes from bug 1578422 are coming in.

Comment 1

[Gian-Carlo Pascutto [:gcp]]

There are older reports with this signature, but all the recent ones are from the same machine (at the same time). So the GPU process keeps crashing over and over again.

Comment 2

[Gian-Carlo Pascutto [:gcp]]

Hmm, why is the crash reporter marking this as:

Process Type content (web)

Even though the SocketProcessChild is crashing?

Comment 3

[Gian-Carlo Pascutto [:gcp]]

Bob observed that the crashing process aren't sandboxed so it's not an issue with not having perms to set up Shmem.

Comment 4

[Gabriele Svelto [:gsvelto] (PTO)]

This is still a thing, it's coming from multiple installations now and the crash reason is always failed to allocate crash reporter shmem.

Comment 5

[Gabriele Svelto [:gsvelto] (PTO)]

This will go away with bug 1614933.

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.