Nvda crashes when selecting whole text in specific source files in Android studio

[PeterLecky]

Actually do not know what causes this. It happens in larger files but not in all large files. I prepared file which is not compillable (see zipped attachment, it defines few constants a lot of times), but this happens also in syntactically correct files.

Steps to reproduce:

1. Open Android studio and attached java file in code editor
2. Press ctrl+a to select whole file
3. Nvda now completely crashes

It is also possible to reproduce this crash from python console

1. Open Android studio and attached java file in code editor
2. invoke python console (nvda+ctrl+z)
3. invoke import textInfos;len(focus.makeTextInfo(textInfos.POSITION_ALL).text)

Actual behavior:

Nvda completely crashes and there are no any relevant information in %tmp%\nvda-old.log

Expected behavior:

NVDA logs, crash dumps and other attachments:

BadConstants.zip

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

Nvda 2024.4

Windows version:

Windows 10 22H2,

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

Android Studio Koala | 2024.1.1 Patch 1
Build #AI-241.18034.62.2411.12071903, built on July 10, 2024
Runtime version: 17.0.11+0--11852314 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 16
Non-Bundled Plugins:
io.wisetime.plugins.window.branch (1.1.0)

Other information about your system:

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.

Reproducible on older versions of NVDA

If NVDA add-ons are disabled, is your problem still occurring?

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

[Adriani90]

@PeterLecky Please test with Android studio 2024.2.1 since INtelliJ is updated there as well. are you still having this issue with that version?
Can you also test with IntelliJ 2024.3 which has been released shortly? Most of the times Android studio lags behind IntelliJ, so IntelliJ current version should always be tested as well when encountering issues with Android Studio in general.

[PeterLecky]

Hello, Upgraded Android studio: Android Studio Ladybug | 2024.2.1 Patch 2 Build #AI-242.23339.11.2421.12550806, built on October 24, 2024 Runtime version: 21.0.3+-12282718-b509.11 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. Toolkit: sun.awt.windows.WToolkit Windows 10.0 GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation Memory: 2048M Cores: 16 Registry: ide.experimental.ui=true i18n.locale= Non-Bundled Plugins: io.wisetime.plugins.window.branch (1.1.0) And it still crashes. I remember that i saw something also in nvda log in the past, latest nvda version crashes silently without any data in the log. I have old records (I talked about it with Tony Malykh in the past because i saw it first time with indent nav) so here it is: IO - inputCore.InputManager.executeGesture (14:22:23.728) - winInputHook (5680): Input: kb(laptop):alt+NVDA+downArrow ERROR - scriptHandler.executeScript (14:22:23.739) - MainThread (7196): error executing script: <bound method EditableIndentNav.script_moveToNextSibling of <NVDAObjects.Dynamic_MyCodeEditorEditableTextWithoutAutoSelectDetectionJABEditableIndentNav object at 0x07EC1D90>> with gesture 'alt+NVDA+down arrow' Traceback (most recent call last):   File "scriptHandler.pyc", line 295, in executeScript   File "C:\Users\Peter\AppData\Roaming\nvda\addons\IndentNav\globalPlugins\indent_nav.py", line 439, in script_moveToNextSibling     self.move(1, [msgEditable])   File "C:\Users\Peter\AppData\Roaming\nvda\addons\IndentNav\globalPlugins\indent_nav.py", line 496, in move     self.moveInEditable(increment, errorMessages[0], unbounded, op, speakOnly=speakOnly, moveCount=moveCount)   File "C:\Users\Peter\AppData\Roaming\nvda\addons\IndentNav\globalPlugins\indent_nav.py", line 499, in moveInEditable     with self.getLineManager() as lm:   File "C:\Users\Peter\AppData\Roaming\nvda\addons\IndentNav\globalPlugins\indent_nav.py", line 304, in __enter__     documentText = document.text   File "baseObject.pyc", line 41, in __get__   File "textInfos\offsets.pyc", line 593, in _get_text   File "NVDAObjects\JAB\__init__.pyc", line 164, in _getTextRange   File "JABHandler.pyc", line 479, in getAccessibleTextRange OSError: exception: access violation writing 0x07F35000

[Adriani90]

What happens if indentnav is disabled? Is still crashing?
Is there any possibility to test with narator?
and I see you enabled experimental UI, at least it‘s set to true. Where does that setting come from? And does it have any effect when you set it to false?

[PeterLecky]

What happens if indentnav is disabled? Is still crashing?

Yes, tested also with all plugins disabled

Is there any possibility to test with narator?

It seems that Narator does not support java applications. Didn't crash after ctrl+a but there is no feedback at all in code editor.

and I see you enabled experimental UI, at least it‘s set to true. Where does that setting come from? And does it have any effect when you set it to false?

It's a new thing in latest version of Android studio, they enabled it for all users by default, it was disabled in older versions and NVDA crashed also in that case. Thanks for your time.

[PeterLecky]

I have few more info. I have installed Jaws (full installer has 1.2GB, unbeliewable) and i can select and copy whole code in code editor without any crashes of jaws.
Peter

[PeterLecky]

Ah... Sorry for closing and thanks for reopening, it was my mistake.

…

On 22. 11. 2024 9:49, Adriani90 wrote: Reopened #17418 <#17418>. — Reply to this email directly, view it on GitHub <https://github.com/ nvaccess/nvda#17418#event-15394258608>, or unsubscribe <https:// github.com/notifications/unsubscribe-auth/ AE36JFGFKKMLFJOG2FC445L2B3V2PAVCNFSM6AAAAABSCFWDH2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGM4TIMRVHA3DAOA>. You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[seanbudd]

It seems likely this is a bug in Java Access Bridge. Unfortunately we are stuck on an out of date version until we upgrade NVDA to 64bit see #16304

[mltony]

cc: @dmitrii-drobotov -in case you can come up with some kind of workaround for this.

[dmitrii-drobotov]

Thanks for the heads-up @mltony. Here are my observations after quickly looking into this:

• I can reproduce it with a basic Java Swing app using the default JTextArea component if I paste the same text there. So it's not specific to Android Studio/IntelliJ.
• The size of the text doesn't seem to be the cause, I tried much larger files with 50000+ lines of code, and with them NVDA works slower or might freeze for a bit, but at least it doesn't crash.
• I also don't get anything related in NVDA logs even with the most verbose level, and the debugger doesn't stop on any uncaught exception before crashing. Does anybody have any tips on how I could debug this?
  If I remember correctly, there was a way to enable more logs in the Java Access Bridge, so I could try looking into this.