Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explorer.exe crashes in Windows 7 when start menu accessed with the mouse. #9435

Closed
Qchristensen opened this issue Apr 2, 2019 · 11 comments · Fixed by #10104
Closed

Explorer.exe crashes in Windows 7 when start menu accessed with the mouse. #9435

Qchristensen opened this issue Apr 2, 2019 · 11 comments · Fixed by #10104
Milestone

Comments

@Qchristensen
Copy link
Member

@Qchristensen Qchristensen commented Apr 2, 2019

Steps to reproduce:

On Windows 7:

  1. Click on the Start button to open the start menu.
  2. Move the mouse over a couple of the items in the start menu as if to select something.

Actual behavior:

Explorer.exe stopped responding, and was restarted by Windows.
Intiailly I used SAPI 5 voice, and the log contained:
"DEBUGWARNING - eventHandler.executeEvent (11:39:07.355):
error executing event: mouseMove on <NVDAObjects.Dynamic_EditableTextWithoutAutoSelectDetectionUIA object at 0x052C8AF0> with extra args of {'y': 991, 'x': 337}
Traceback (most recent call last):
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in init
File "eventHandler.pyo", line 100, in next
File "NVDAObjects_init_.pyo", line 928, in event_mouseMove
File "documentBase.pyo", line 24, in makeTextInfo
File "NVDAObjects\UIA_init_.pyo", line 314, in init
COMError: (-2147220991, 'An event was unable to invoke any of the subscribers', (None, None, None, 0, None))"

Full log: Win7Explorerlog.txt

I then restarted the computer, changed the synth to eSpeak and repeated with the same result. It took about 10 or 15 seconds to crash this time and in the meantime reported each menu item as the mouse moved over it. After reading the last menu item before crashing, the log reads:

DEBUGWARNING - watchdog.watcher (12:53:44.414):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui_init
.pyo", line 1003, in Notify
File "core.pyo", line 491, in run
File "mouseHandler.pyo", line 257, in pumpAll
File "mouseHandler.pyo", line 223, in executeMouseMoveEvent
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in init
File "eventHandler.pyo", line 100, in next
File "NVDAObjects_init_.pyo", line 928, in event_mouseMove
File "documentBase.pyo", line 24, in makeTextInfo
File "NVDAObjects\UIA_init_.pyo", line 314, in init

DEBUGWARNING - eventHandler.executeEvent (12:53:44.584):
error executing event: mouseMove on <NVDAObjects.Dynamic_EditableTextWithoutAutoSelectDetectionUIA object at 0x050C2C30> with extra args of {'y': 988, 'x': 139}
Traceback (most recent call last):
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in init
File "eventHandler.pyo", line 100, in next
File "NVDAObjects_init_.pyo", line 928, in event_mouseMove
File "documentBase.pyo", line 24, in makeTextInfo
File "NVDAObjects\UIA_init_.pyo", line 314, in init
COMError: (-2147220991, 'An event was unable to invoke any of the subscribers', (None, None, None, 0, None))

This has been reported by several users with several other scenarios (all involving explorer), but using the mouse in the start menu seems a consistent way to trigger it.

Expected behavior:

Explorer shouldn't crash.

System configuration

NVDA installed/portable/running from source:

NVDA version:

NVDA 2019.1 installed

Windows version:

Windows 7 Home Premium, version 6.1, build 7601, service pack 1.

Name and version of other software in use when reproducing the issue:

Other information about your system:

Other questions

Does the issue still occur after restarting your PC?

Yes.

Have you tried any other versions of NVDA?

Previous versions of NVDA (2018.4.1) do not produce a crash, and repeating without NVDA running there is no crash.

@Qchristensen
Copy link
Member Author

@Qchristensen Qchristensen commented Apr 2, 2019

I also meant to add, accessing the Start menu with the keyboard works fine.

@DrSooom
Copy link

@DrSooom DrSooom commented Apr 2, 2019

Does this issue also occur if mouse tracking (NVDA+M) is disabled?

@Brian1Gaff
Copy link

@Brian1Gaff Brian1Gaff commented Apr 2, 2019

@Qchristensen
Copy link
Member Author

@Qchristensen Qchristensen commented Apr 2, 2019

With mouse tracking disabled, the crash doesn't happen.

Brian, re crashes which require a reboot - in the %temp% folder, where the nvda.log is kept, there is usually an nvda-old.log which is the log from the previous time NVDA was run. If you look for that file when you restart the computer, it should have just about everything NVDA recorded about what it was doing. Also re the problems with issues which can be hard to reproduce, that was why I was specific in how to repro this one. This one definitely seems to be triggered by the mouse.

@Adriani90
Copy link
Collaborator

@Adriani90 Adriani90 commented Apr 9, 2019

@leonardder
Copy link
Collaborator

@leonardder leonardder commented Aug 16, 2019

Ah, looks like i"m the author of this crash, see #8572.

Disabling mouse tracking seems to be an acceptable work around for now, but I"ll provide a fix anyway.

@lukaszgo1
Copy link
Contributor

@lukaszgo1 lukaszgo1 commented Aug 16, 2019

I don't know if it has the same underlying cause, but for me even with mouse tracking disabled it is sufficient to route mouse to start menu search field in Windows 7 to cause explorer to crash. When it crashes it takes NVDA with it, so the only way to go back to the working condition is to kill explorer.exe from another account.

@leonardder
Copy link
Collaborator

@leonardder leonardder commented Aug 16, 2019

@lukaszgo1: yes, this is expected behavior according to the cause of the crash, which is a freeze in the UIA client library according to earlier findings. We thought that these were fixed, but it seems like they aren't.
A try build is on the way.

@leonardder
Copy link
Collaborator

@leonardder leonardder commented Aug 16, 2019

@lukaszgo1
Copy link
Contributor

@lukaszgo1 lukaszgo1 commented Aug 16, 2019

I can confirm that routing mouse to the start menu search box no longer crashes explorer with this build.

@Brian1Gaff
Copy link

@Brian1Gaff Brian1Gaff commented Aug 16, 2019

Hi a couple of weeks ago we had this crash 49 times while attempting to copy some files with the mouse with nvda loaded, so I'll be glad to get a fixed snap asap to save my producers sanity!
Brian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants