Closed Bug 1323498 Opened 5 years ago Closed 3 months ago

Crash in mozilla::ipc::MessageChannel::OnChannelErrorFromLink

Categories

(Core :: IPC, defect, P2)

53 Branch
Unspecified
Windows 8
defect

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
firefox53 --- wontfix
firefox54 --- fixed

People

(Reporter: alex_mayorga, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, nightly-community, regression)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-c5599f17-631b-45b8-9f58-56bf22161213.
=============================================================

¡Hola!

This is top 28 crash for Nightly as of today. 25 more crashes at https://crash-stats.mozilla.com/signature/?product=Firefox&signature=mozilla%3A%3Aipc%3A%3AMessageChannel%3A%3AOnChannelErrorFromLink

¡Gracias!
Alex

Crashing Thread (1)
Frame 	Module 	Signature 	Source
0 	xul.dll 	mozilla::ipc::MessageChannel::OnChannelErrorFromLink() 	ipc/glue/MessageChannel.cpp:2155
1 	xul.dll 	mozilla::ipc::ProcessLink::OnChannelConnectError() 	ipc/glue/MessageLink.cpp:355
2 	xul.dll 	mozilla::detail::RunnableMethodImpl<void ( mozilla::net::CacheEntry::*)(void), 1, 0>::Run() 	obj-firefox/dist/include/nsThreadUtils.h:826
3 	xul.dll 	MessageLoop::RunTask(already_AddRefed<mozilla::Runnable>) 	ipc/chromium/src/base/message_loop.cc:346
4 	xul.dll 	MessageLoop::DeferOrRunPendingTask(MessageLoop::PendingTask&&) 	ipc/chromium/src/base/message_loop.cc:354
5 	xul.dll 	MessageLoop::DoWork() 	ipc/chromium/src/base/message_loop.cc:429
6 	xul.dll 	base::MessagePumpForIO::DoRunLoop() 	ipc/chromium/src/base/message_pump_win.cc:436
7 	xul.dll 	base::MessagePumpWin::Run(base::MessagePump::Delegate*) 	ipc/chromium/src/base/message_pump_win.h:80
8 	xul.dll 	MessageLoop::RunHandler() 	ipc/chromium/src/base/message_loop.cc:225
9 	xul.dll 	MessageLoop::Run() 	ipc/chromium/src/base/message_loop.cc:205
10 	xul.dll 	base::Thread::ThreadMain() 	ipc/chromium/src/base/thread.cc:180
11 	xul.dll 	`anonymous namespace'::ThreadFunc 	ipc/chromium/src/base/platform_thread_win.cc:28
12 	kernel32.dll 	BaseThreadInitThunk 	
13 	xul.dll 	mozilla::detail::VectorImpl<mozilla::Telemetry::HangHistogram, 4, mozilla::MallocAllocPolicy, 0>::moveConstruct<mozilla::Telemetry::HangHistogram>(mozilla::Telemetry::HangHistogram*, mozilla::Telemetry::HangHistogram*, mozilla::Telemetry::HangHistogram*) 	obj-firefox/dist/include/mozilla/Vector.h:112
This has now moved up to the #5 top overall browser crash in nightly: http://bit.ly/2lbLLe0. It appears to be a startup crash that affects Windows and Mac.
Some of the correlations look like they could be interesting:
(100.0% in signature vs 16.01% overall) process_type = null [100.0% vs 05.13% if startup_crash = null]
(100.0% in signature vs 24.41% overall) startup_crash = null [100.0% vs 07.81% if process_type = null]
(87.50% in signature vs 00.34% overall) Module "smci64.dll" = true [93.10% vs 00.50% if platform_version = 10.0.14393]
(96.88% in signature vs 17.62% overall) Module "urlmon.dll" = true
(96.88% in signature vs 45.52% overall) Module "comctl32.dll" = true [96.88% vs 23.62% if platform_pretty_version = Windows 8.1]
(51.56% in signature vs 01.67% overall) adapter_driver_version_clean = 4425 [80.49% vs 03.48% if adapter_vendor_id = Intel Corporation]
(51.56% in signature vs 01.67% overall) adapter_driver_version = 10.18.10.4425 [80.49% vs 03.48% if adapter_vendor_id = Intel Corporation]

smci64.dll looks like it is some kind of malware.
I looked through a few of these crashes, and they look like they are in the content process, despite not having process type annotations on the crash. In a number of them, the main thread is running 	mozilla::dom::PContentChild::SendPCrashReporterConstructor(), which gets called in ContentChild::Init(). So we're early in content process startup.
See Also: → 1339338
We should probably blocklist Search Module Plus Update service.
Depends on: 1339908
Priority: -- → P2
Depends on: 1397419
Blocks: 1397419
No longer depends on: 1397419

The stack from comment #0 was removed in bug 1706374, so closing this in favor of bug 1719496.

Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → INCOMPLETE
QA Whiteboard: qa-not-actionable
You need to log in before you can comment on or make changes to this bug.