Closed
Bug 1579874
Opened 5 years ago
Closed 5 years ago
SocketProcess misidentified as Content Process in crash reports
Categories
(Core :: Networking, defect, P2)
Tracking
()
RESOLVED
FIXED
mozilla71
| Tracking | Status | |
|---|---|---|
| firefox71 | --- | fixed |
People
(Reporter: gcp, Assigned: kershaw)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
From Bug 1579800 - Crash in [@ mozilla::ipc::CrashReporterClient::InitSingleton<T>]
Crash signature:
https://crash-stats.mozilla.org/report/index/4e06d931-55b5-489f-87b7-4a46a0190908
Notice that the process is described as:
Process Type content (web)
Even though the crash is in:
bool mozilla::net::SocketProcessChild::Init(unsigned long, const char*, class MessageLoop*, class IPC::Channel*)
|
||
Comment 1•5 years ago
|
||
Kershaw, can you take a look?
|
Assignee | |
Updated•5 years ago
|
Assignee: nobody → kershaw
Flags: needinfo?(kershaw)
|
|
Assignee | |
Comment 2•5 years ago
|
||
Pushed by kjang@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f627d416294f Use the correct process type for socket process r=jld
|
||
Comment 4•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
You need to log in
before you can comment on or make changes to this bug.
Description
•