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
NVDA's "mouse tracking" causes NOD32 Antivirus to crash #1393
Comments
Comment 1 by k_kolev1985 on 2011-02-26 21:32 Even so, the first part of the problem still remains and unfortunately it is harder to reproduce than the second one. But I'll be happy to help you in any way I can. |
Comment 2 by Bernd on 2013-05-07 15:45 |
Comment 3 by k_kolev1985 on 2013-05-07 17:08 |
Comment 4 by k_kolev1985 on 2014-11-11 08:13 |
Comment 5 by jteh on 2014-11-11 10:03 |
Reported by k_kolev1985 on 2011-02-26 16:08
I've started using NOD32 Antivirus in May 2010. A few months later I've started using NVDA regularly as well (previously I was using another screen reader as my primary one). Since I've started using NVDA, I've noticed that while NOD32 Antivirus displays some of its standalone windows (update notifications, virus alerts, etc.), there's a possibility that the NOD32 GUI module (egui.exe) may crash with the standard error message of Windows 7 that a program stopped working. And I may say that I'm at least partially blaming NVDA for this crash, because while I was using the other screen reader (JAWS) such crashes did not occur. I think that those crashes may be caused by NVDA's "mouse tracking", but I'm not sure about it.
Recently (in the latest NVDA snapshots) however, things got worse. If I point the mouse cursor in the list of scan results (e.g. after a "context menu" scan), the NOD32 GUI module (egui.exe) crashes. This did not occur previously (with NVDA 2010.2 for example). I'm using NVDA snapshot r4120 and NOD32 Antivirus v4.2.71.2 (in bulgarian). This time I'm 100% sure that NVDA's "mouse tracking" is the culprit, because when I turn it off, there's no crashing of egui.exe.
Steps to reproduce at least the second part of the issue (the first part is difficult to reproduce because it doesn't happen every time):
The text was updated successfully, but these errors were encountered: