Repository navigation
Closed
Labels
p3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Description
Steps to reproduce:
- Go to jetbrains.com/idea to download and install IntelliJ IDEA Community Edition 2021.2.3;
- After installation, follow the default settings and create a new project arbitrarily;
- Exit IntelliJ IDEA;
- Open IntelliJ IDEA again, it will take a while to load, press Windows + M to minimize to the desktop during this time;
Actual behavior:
During the execution of step (4), you will receive a large number of errors from NVDA when you minimize to the desktop. The log snippet is as follows:
ERROR - queueHandler.flushQueue (09:19:24.473) - MainThread (16392):
Error in func event_stateChange
Traceback (most recent call last):
File "queueHandler.pyc", line 55, in flushQueue
File "JABHandler.pyc", line 709, in event_stateChange
File "NVDAObjects\__init__.pyc", line 85, in __call__
File "NVDAObjects\JAB\__init__.pyc", line 231, in __init__
File "NVDAObjects\window\__init__.pyc", line 167, in __init__
ValueError: invalid or not specified window handle
IntelliJ IDEA will be opened after you receive dozens of errors.
Expected behavior:
NVDA has no error messages and IntelliJ IDEA should open smoothly,.
System configuration
NVDA installed/portable/running from source:
installed and portable
NVDA version:
NVDA2021.3 Beta2
Windows version:
Windows 10 21H1 (x64) build 19043.1288
Name and version of other software in use when reproducing the issue:
IntelliJ IDEA Community Edition 2021.2.3
Other information about your system:
- CPU: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz 1.90 GHz
- RAM: 16.0 GB
- Disk: 512 GB SSD
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
The latest Alpha version can also be reproduced
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
Metadata
Metadata
Assignees
Labels
p3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Activity
Brian1Gaff commentedon Nov 8, 2021
cary-rowen commentedon Nov 8, 2021
Yes, this is a program written in Java.
cary-rowen commentedon Nov 9, 2021
@michaelDCurran @LeonarddeR
Do you have any thoughts on this?
cary-rowen commentedon Dec 25, 2021
cc @seanbudd
Could you please take a look at this issue?
dpy013 commentedon Dec 28, 2021
The same problem was encountered when using jetbrains
mwhapples commentedon Jun 13, 2022
I have started taking a look at this. Something very important in reproducing which I did not initially appreciate, is needing to minimise the windows with Windows+M. If you do not minimise the windows then you do not get the errors.
cary-rowen commentedon Jun 13, 2022
thanks @mwhapples
Yes, minimization is a necessary step.
mwhapples commentedon Jun 14, 2022
@cary-rowen I have created a fix for this see pull request #13796 could you try it to see if that fixes the issue for you, in particular the speed of IntelliJ loading. The best I could come up with is to ignore the events causing the errors. It seems like Java Access Bridge cannot provide the window handle for Java windows which have never been shown on the screen. By ignoring the events it means NVDA will not spend time processing the errors and so should not unnecessarily slow down IntelliJ. As IntelliJ is minimised at this point ignoring these events should not impact on user experience.
cary-rowen commentedon Jun 14, 2022
@mwhapples
Thanks for your effort, I tested build #13796 and it worked fine for me, thanks again.
Hopefully this will be part of 2022.2 if possible.
mwhapples commentedon Jun 14, 2022
That is great news. I suspect that this won't be included in 2022.2 because I think that has already been branched. Personally knowing the size of this change and its limited scope for causing unrelated issues, I would port it to the 2022.2 branch but I don't get to make that decission.
Ignore events where Java Access Bridge is unable to provide a window …