Results Window Goes "Blank"

[Troesler-illuminate]

Issue Type: Performance Issue

Often the results window of a query will go "blank" meaning that individual cell valures are not shown, but the grid lines will still be drawn. To fix this I usually have to drag around the vertical and/or horizontal scroll bars to get the table to be drawn correctly for a section of data. I am not sure if this is a function of row count or column count, but it happens on most tables/result sets and is preventing me from reasonably switching from SSMS to Azure Data Studio as my "daily driver".

For reference, this specific result set had 74k rows and 150 columns, but it has happened on lesser result sets as well.

I tried disabling all extensions and this still occurred. I also limited to 10k rows and the problem still occurred. Here is a screenshot of the behavior:

Steps to reproduce

1. Query a table in your database with a decent amount of rows and columns
2. Scroll through the results window in either (or both) the horizontal and vertical directions
3. Eventually you will notice the cells becoming blank and not displaying data

Azure Data Studio version: azuredatastudio 1.36.2 (2299a76973585fa962cfd06e8acab4abb41567de, 2022-05-19T04:18:20.649Z) OS version: Windows_NT x64 10.0.19044 Restricted Mode: No

System Info

|Item|Value| |---|---| |CPUs|11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 2803)| |GPU Status|2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|31.69GB (22.03GB free)| |Process Argv|| |Screen Reader|no| |VM|0%|

Process Info

``` CPU % Mem MB PID Process 0 91 64532 azuredatastudio main 0 86 10224 shared-process 0 71 26568 ptyHost 0 140 20576 gpu-process 0 82 65060 window (Issue Reporter) 0 193 65300 window (● SQLQuery_1 - 1323-TROESLER-L.sis_api (Integrated) - Azure Data Studio) 0 161 46640 extensionHost 0 71 19596 "C:\Program Files\Azure Data Studio\azuredatastudio.exe" "c:\Program Files\Azure Data Studio\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=46640 0 47 27056 dotnet tool run dotnet-interactive -- notebook-parser 0 25 31312 "C:\Program Files\dotnet\dotnet.exe" C:\Users\Tyler\.nuget\packages\microsoft.dotnet-interactive\1.0.317502\tools/net6.0/any/Microsoft.DotNet.Interactive.App.dll notebook-parser 0 11 35648 console-window-host (Windows internal process) 0 35 52148 "c:\Program Files\Azure Data Studio\resources\app\extensions\mssql\sqltoolsservice\Windows\3.0.0-release.238\MicrosoftSqlToolsCredentials.exe" --locale en --log-file c:\Users\Tyler\AppData\Roaming\azuredatastudio\logs\20220603T102636\exthost1\Microsoft.mssql\credentialstore.log --tracing-level Critical 0 11 41172 console-window-host (Windows internal process) 0 37 56740 "c:\Program Files\Azure Data Studio\resources\app\extensions\mssql\sqltoolsservice\Windows\3.0.0-release.238\SqlToolsResourceProviderService.exe" --locale en --log-file c:\Users\Tyler\AppData\Roaming\azuredatastudio\logs\20220603T102636\exthost1\Microsoft.mssql\resourceprovider.log --tracing-level Critical 0 11 22308 console-window-host (Windows internal process) 0 165 71092 "c:\Program Files\Azure Data Studio\resources\app\extensions\mssql\sqltoolsservice\Windows\3.0.0-release.238\MicrosoftSqlToolsServiceLayer.exe" --locale en --log-file c:\Users\Tyler\AppData\Roaming\azuredatastudio\logs\20220603T102636\exthost1\Microsoft.mssql\sqltools.log --tracing-level Critical 0 11 18000 console-window-host (Windows internal process) 0 38 81364 utility ```

Workspace Info

``` ; ```

Extensions (10)

Extension|Author (truncated)|Version ---|---|--- admin-tool-ext-win|Mic|0.0.3 profiler|Mic|0.11.0 query-history|Mic|0.1.0 schema-compare|Mic|1.13.1 sql-assessment|Mic|0.6.1 sql-database-projects|Mic|0.16.1 dotnet-interactive-vscode|ms-|1.0.3175020 jupyter|ms-|2021.8.1046824664 azdata-sanddance|msr|3.3.0 vscodeintellicode|Vis|1.2.1

[alanrenmsft]

@Troesler-illuminate I did experience the slowness comparing to small dataset, but eventually, it will be rendered after a second or so. for you how long does it stay like that for?

[Troesler-illuminate]

@alanrenmsft I just tested with the latest build and it offers similar behavior to what you included in your screen recording. Before it would just stay like that until I moved the scroll bar one way or the other. The performance in the latest build is much better/acceptable!

[alanrenmsft]

great to know, thanks!

[PaddySe]

This problem is still there, even when only a couple of rows are returned from the query. It usually helps to switch to the Messages tab and back, but it is highly annoying having to switch back and forth between mouse and keyboard just to be able to see the results.