search

tomoki1207 / vscode-pdfviewer

Show PDF preview in VSCode.
https://marketplace.visualstudio.com/items/tomoki1207.pdf
Other
295 stars 70 forks source link

vscode-pdf in WSL2 dont work properly and sometimes just black out #87

Open TeddyHuang-00 opened 3 years ago

TeddyHuang-00 commented 3 years ago

Issue Type: Bug

when opening pdf files in the workspace under WSL2(Windows Subsystem for Linux 2), it doesn't show the content as it does when opening same workspace and same files in Windows using the same extension. And even at times they DO display something, it show something like the feature outline of the extension (all displayed as buttons and text areas and even a progress bar that never progress reading "Preparing document for printing", see in the screenshots below image image )

Extension version: 1.1.0 VS Code version: Code 1.52.1 (ea3859d4ba2f3e577a159bc91e3074c5d85c0523, 2020-12-16T16:34:46.910Z) OS version: Windows_NT x64 10.0.19042 Remote OS version: Linux x64 4.19.128-microsoft-standard

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)| |GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
protected_video_decode: enabled
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|15.92GB (7.83GB free)| |Process Argv|--crash-reporter-id fa7608df-2216-4091-9536-76caee63a1ef| |Screen Reader|no| |VM|0%| |Item|Value| |---|---| |Remote|WSL: Debian| |OS|Linux x64 4.19.128-microsoft-standard| |CPUs|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)| |Memory (System)|12.43GB (11.08GB free)| |VM|0%|
A/B Experiments ``` vsliv368cf:30146710 vsreu685:30147344 openlogontheside:30221877 python383:30185418 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492:30211401 wsl2prompt:30224612 pythonvsdeb440cf:30242243 unusedpromptcf:30224611 folderexplorercf:30224615 openfilemenucf:30224648 pythonvsded773cf:30236630 pythonvspyt600cf:30241728 ```
Bambie07 commented 3 years ago

I got the same problem after restarting vscode. Using Windows and WSL2 with Ubuntu 20.04. Reinstall didn't help.

TeddyHuang-00 commented 3 years ago

I got the same problem after restarting vscode. Using Windows and WSL2 with Ubuntu 20.04. Reinstall didn't help.

After trying solutions like reinstall vscode and Debian 10 distro in WSL2, I found by accident that my problem was raised by my VPN client clash. I got this problem along with dysfunction of jupyter-notebook extension since the day I set clash to auto start with Windows. I didn't figure out why, but if clash is compatible with distros under WSL1, then it might be issue from the communication between WSL2 VM and the Windows and may be the cause for many other similar problems. Don't know if this can help you

TeddyHuang-00 commented 3 years ago

I got the same problem after restarting vscode. Using Windows and WSL2 with Ubuntu 20.04. Reinstall didn't help.

After trying solutions like reinstall vscode and Debian 10 distro in WSL2, I found by accident that my problem was raised by my VPN client clash. I got this problem along with dysfunction of jupyter-notebook extension since the day I set clash to auto start with Windows. I didn't figure out why, but if clash is compatible with distros under WSL1, then it might be issue from the communication between WSL2 VM and the Windows and may be the cause for many other similar problems. Don't know if this can help you

BTW, since vscode seems to be using Node.js for the communication between WSL2 and Windows client, I guess it can also harm WSL in similar way. But in my case, simply closing clash can remove all the problems