nvda icon indicating copy to clipboard operation
nvda copied to clipboard

Holding down the down arrow in a large document causes nvda to crash and exit

Open cary-rowen opened this issue 2 years ago • 13 comments

1.txt.zip nvda-old.log

Steps to reproduce:

  1. Download the attached test sample: 1.txt.zip and remove the .zip extension;
  2. Or use the following python code to generate a document identical to the test sample
with open(r'd:1.txt', 'w', encoding = 'utf-8') as f:
    f.write('[I 211209 00:10:40 web:2239] 200 GET / (::1) 335.00ms\n' * 300000)
  1. Use Windows notepad to open 1.txt;
  2. Keep holding down the down arrow;
  3. If you configure "Play a sound for logged errors" to yes you will hear the error sound and nvda will exit.

Actual behavior:

nvda exit

p.s. In the same situation narrator works fine.

Expected behavior:

nvda doesn't exit and can report the content of the line the cursor is on

System configuration

NVDA installed/portable/running from source:

installed and portable

NVDA version:

2021.3.1 and Alpha

Windows version:

Windows 10 21H2 (x64) build 19044.1526

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

None

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.

No

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

cary-rowen avatar Feb 13 '22 09:02 cary-rowen

I don't think you can add attachments here.

Brian1Gaff avatar Feb 13 '22 09:02 Brian1Gaff

@Brian1Gaff

hello, i guess it doesn't matter, because i provided the python code that generates the test samples

Thanks

cary-rowen avatar Feb 13 '22 09:02 cary-rowen

Note that the log contained in this issue has not the add-ons disabled.

However, I have reproduced this issue easily with NVDA 2021.3.1 installed version, add-ons disabled (Windows 10 2004 (x64) build 19041.388). Here is the log: nvda-old.log

This bug does not seem new. I have also reproduced it with NVDA 2020.4 temporary copy (from installer), add-ons disabled.

CyrilleB79 avatar Feb 13 '22 21:02 CyrilleB79

Hello @CyrilleB79 Thanks for investigating this issue. Grateful

cary-rowen avatar Feb 14 '22 05:02 cary-rowen

To clarify, I have just done additional tests and provided the missing information (log with add-ons disabled, test on older release). But I have no clue on how to investigate it so I will not go further.

For information, NVDA crashes but I have not found any nvda dumpfile in %tmp%.

CyrilleB79 avatar Feb 14 '22 09:02 CyrilleB79

@seanbudd Will you open a PR to address this issue?

cary-rowen avatar Jul 14 '22 09:07 cary-rowen

@cary-rowen it is unlikely to be addressed by NV Access until at least 2022.4

seanbudd avatar Jul 15 '22 01:07 seanbudd

This is still reproducible with NVDA 2022.3.1 or 2022.4. Note that #11597 and the refereced PR #11478 give a good overview of what could cause this issue. Even though the issues described there relate more to text selection, I think the root could come from the same VK_NONE sending issue for arrow key navigation and thus might not be limited to modifier keys. cc: @michaelDCurran.

Adriani90 avatar Mar 01 '23 14:03 Adriani90

Is this still an issue with 2024.1?

seanbudd avatar Apr 29 '24 02:04 seanbudd

No this seems to work as expected with NVDA last alpha. No freeze or chrash when moving or selecting very long snippets with NVDA in last Windows Notepad version.

Closing as works for me.

Adriani90 avatar Apr 29 '24 06:04 Adriani90

Hello @seanbudd

For me I no longer get crashes, but still see errors in the log: RecursionError: maximum recursion depth exceeded while calling a Python object

I agree to close this.

Hi @Adriani90

thank you for your reply. I hope you can wait a little longer for the original reporter's comments when facing the same thing in the future. This is especially true if the original reporter is often active. Doing so respects other contributors and ensures that each issue is treated with a more rigorous attitude. Instead of choosing to immediately close an issue that may not be reproducible for you just because you can close any issue. As you can see, @seanbudd didn't do this.

Thanks

cary-rowen avatar Apr 29 '24 06:04 cary-rowen

More specifically on my side: no more crash, but the errors are still logged. NVDA recovers quite quickly though.

CyrilleB79 avatar Apr 29 '24 09:04 CyrilleB79

Considering errors are still logged I am reopening this and changing it to a p4

seanbudd avatar Apr 29 '24 23:04 seanbudd