1403590 - Crashes in nvdahelperremote.dll in Firefox 57

Status: RESOLVED WONTFIX

(Core :: Disability Access APIs, defect)

Description

[[:philipp]]

This bug was filed from the Socorro interface and is 
report bp-b7b89e8d-cd05-4cc5-ac2b-a16f20170927.
=============================================================
Crashing Thread (0)
Frame 	Module 	Signature 	Source
0 		@0xf078e5d 	
Ø 1 	nvdahelperremote.dll 	nvdahelperremote.dll@0x9045 	
2 	ntdll.dll 	RtlLeaveCriticalSection 	
3 	xul.dll 	mozilla::widget::InputContext::~InputContext() 	
Ø 4 	nvdahelperremote.dll 	nvdahelperremote.dll@0x33071 	
5 	user32.dll 	__ClientCallWinEventProc 	
6 	ntdll.dll 	KiUserCallbackDispatcher 	
7 	ntdll.dll 	KiUserApcDispatcher 	
8 	xul.dll 	mozilla::a11y::DocAccessibleParent::RecvStateChangeEvent(unsigned __int64 const&, unsigned __int64 const&, bool const&) 	accessible/ipc/DocAccessibleParent.cpp:252
9 	xul.dll 	mozilla::a11y::PDocAccessibleParent::OnMessageReceived(IPC::Message const&) 	ipc/ipdl/PDocAccessibleParent.cpp:316
10 	xul.dll 	mozilla::dom::PContentParent::OnMessageReceived(IPC::Message const&) 	ipc/ipdl/PContentParent.cpp:3180
11 	xul.dll 	mozilla::ipc::MessageChannel::DispatchAsyncMessage(IPC::Message const&) 	ipc/glue/MessageChannel.cpp:2115
12 	xul.dll 	mozilla::ipc::MessageChannel::DispatchMessageW(IPC::Message&&) 	ipc/glue/MessageChannel.cpp:2045
13 	xul.dll 	mozilla::ipc::MessageChannel::RunMessage(mozilla::ipc::MessageChannel::MessageTask&) 	ipc/glue/MessageChannel.cpp:1891
14 	xul.dll 	mozilla::ipc::MessageChannel::MessageTask::Run() 	ipc/glue/MessageChannel.cpp:1924
15 	xul.dll 	nsThread::ProcessNextEvent(bool, bool*) 	xpcom/threads/nsThread.cpp:1039
16 	xul.dll 	mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) 	ipc/glue/MessagePump.cpp:97
17 	xul.dll 	MessageLoop::RunHandler() 	ipc/chromium/src/base/message_loop.cc:319
18 	xul.dll 	MessageLoop::Run() 	ipc/chromium/src/base/message_loop.cc:299
19 	xul.dll 	nsBaseAppShell::Run() 	widget/nsBaseAppShell.cpp:158
20 	xul.dll 	nsAppShell::Run() 	widget/windows/nsAppShell.cpp:230
21 	xul.dll 	nsAppStartup::Run() 	toolkit/components/startup/nsAppStartup.cpp:288
22 	xul.dll 	XREMain::XRE_mainRun() 	toolkit/xre/nsAppRunner.cpp:4701
23 	xul.dll 	XREMain::XRE_main(int, char** const, mozilla::BootstrapConfig const&) 	toolkit/xre/nsAppRunner.cpp:4865
24 	xul.dll 	XRE_main(int, char** const, mozilla::BootstrapConfig const&) 	toolkit/xre/nsAppRunner.cpp:4960
25 	xul.dll 	mozilla::BootstrapImpl::XRE_main(int, char** const, mozilla::BootstrapConfig const&) 	toolkit/xre/Bootstrap.cpp:45
26 	firefox.exe 	wmain 	toolkit/xre/nsWindowsWMain.cpp:115
27 	firefox.exe 	__scrt_common_main_seh 	f:/dd/vctools/crt/vcstartup/src/startup/exe_common.inl:253
28 	kernel32.dll 	BaseThreadInitThunk 	
29 	ntdll.dll 	__RtlUserThreadStart 	
30 	ntdll.dll 	_RtlUserThreadStart

various crash reports with signatures containing nvdahelperremote.dll are spiking up in 57.0b3 - the first 57 release pushed to users on the beta channel, so far from users on windows 7 and 8.1.
accessibility is obviously shown as turned on in all of these reports...

Comment 1

[Jim Mathies [:jimm]]

Based on the crash graph, appears to be a one off. Maybe someone testing?

Comment 2

[[:philipp]]

the crash graph hasn't caught on yet - b3 is only out there for a bit more than a day:
https://crash-stats.mozilla.com/search/?signature=%5Envdahelperremote.dll&version=57.0b&date=%3E%3D2017-06-01T&_sort=-date&_facets=signature&_facets=version&_facets=user_comments&_facets=uptime&_facets=adapter_vendor_id&_facets=build_id&_facets=install_time&_facets=platform_pretty_version&_facets=useragent_locale&_facets=release_channel&_facets=cpu_arch&_facets=process_type&_facets=moz_crash_reason&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-install_time

Comment 3

[(No longer employed by Mozilla) Aaron Klotz]

That's odd that we don't have NVDA symbols for this... When he was still at NVAccess, Jamie worked with Ted to export their symbols into Socorro for us...

Comment 4

[(No longer employed by Mozilla) Aaron Klotz]

Jamie and I have been digging, and none of the nvdaHelperRemote.dll modules contain version information. Jamie says that version info was added to NVDA DLLs in September of 2016, so we believe that these crashes are occurring because of people running beta with outdated, incompatible versions of NVDA.

Comment 5

[(No longer employed by Mozilla) Aaron Klotz]

Jim, I know we were talking about potentially blocking old versions of NVDA in addition to JAWS. Thoughts?

Comment 6

[David Bolter [:davidb] (NeedInfo me for attention)]

If you run into this bug please update your copy of NVDA.