/CC @isidorn
Issue Type: Bug
I'm unsure if this is an NVDA or a Vs Code bug, so have also cross-posted in nvaccess/nvda#12125
- Copy the contents of crash.txt into a new document in Vs Code
- With NVDA running, press ctrl+end to go to the bottom, and press up arrow to read upwards.
Expected: it says }, as that is the end of the JSON output.
Actual: it read some data that belongs to lines further up. I think this is caused by that underlying chromium bug that prevents long files from being read properly.
More critically, it causes Vs Code to hang and NVDA to also hang as well. The only way to recover is to force kill Vs Code, which could be difficult if NVDA hangs as well.
NVDA version: alpha-21802,5678c8be
VS Code version: Code - Insiders 1.55.0-insider (567b82a, 2021-03-05T05:22:52.277Z)
OS version: Windows_NT x64 10.0.19041
Remote OS version: Linux x64 5.4.72-microsoft-standard-WSL2
System Info
| Item |
Value |
| CPUs |
AMD Ryzen 7 PRO 4750U with Radeon Graphics (16 x 1697) |
| GPU Status |
2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled |
| Load (avg) |
undefined |
| Memory (System) |
31.23GB (18.49GB free) |
| Process Argv |
--folder-uri=vscode-remote://wsl+Ubuntu/home/dickson/source/api-notarise-formsg --remote=wsl+Ubuntu --crash-reporter-id 1304d64e-abdb-456c-beb6-72c33120f731 |
| Screen Reader |
yes |
| VM |
0% |
| Item |
Value |
| Remote |
WSL: Ubuntu |
| OS |
Linux x64 5.4.72-microsoft-standard-WSL2 |
| CPUs |
AMD Ryzen 7 PRO 4750U with Radeon Graphics (16 x 1696) |
| Memory (System) |
24.45GB (20.49GB free) |
| VM |
0% |
Extensions (8)
| Extension |
Author (truncated) |
Version |
| remote-containers |
ms- |
0.163.0 |
| remote-ssh |
ms- |
0.65.0 |
| remote-ssh-edit |
ms- |
0.65.0 |
| remote-wsl |
ms- |
0.54.0 |
| vscode-remote-extensionpack |
ms- |
0.20.0 |
| vscode-eslint |
dba |
2.1.14 |
| gitlens |
eam |
11.3.0 |
| prettier-vscode |
esb |
5.9.2 |
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30263608
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30244315
pythonvsdeb440:30224570
pythonvsded773:30223139
pythonvspyt875:30259475
pythonvsnew554:30265444
pythontb:30258533
vscoresta800cf:30265948
vspre833cf:30267465
/CC @isidorn
Issue Type: Bug
I'm unsure if this is an NVDA or a Vs Code bug, so have also cross-posted in nvaccess/nvda#12125
Expected: it says
}, as that is the end of the JSON output.Actual: it read some data that belongs to lines further up. I think this is caused by that underlying chromium bug that prevents long files from being read properly.
More critically, it causes Vs Code to hang and NVDA to also hang as well. The only way to recover is to force kill Vs Code, which could be difficult if NVDA hangs as well.
NVDA version: alpha-21802,5678c8be
VS Code version: Code - Insiders 1.55.0-insider (567b82a, 2021-03-05T05:22:52.277Z)
OS version: Windows_NT x64 10.0.19041
Remote OS version: Linux x64 5.4.72-microsoft-standard-WSL2
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Extensions (8)
A/B Experiments