Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension appears to break TypeScript within WSL #64

Open
MoonstarCoding opened this issue May 13, 2024 · 4 comments
Open

Extension appears to break TypeScript within WSL #64

MoonstarCoding opened this issue May 13, 2024 · 4 comments
Assignees

Comments

@MoonstarCoding
Copy link

MoonstarCoding commented May 13, 2024

Type: Bug

Started remote host session in WSL and attempted to develop TypeScript v5.4.5 application. Noticed TypeScript intellisense was infinitely Loading and extensions were not being activated. Usage of Extension Bisect traced down to Regex extension.

Extension version: 0.4.0
VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:13:33.891Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Connection to 'wsl+ubuntu' could not be established

System Info
Item Value
CPUs 12th Gen Intel(R) Core(TM) i7-12850HX (24 x 2419)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Load (avg) undefined
Memory (System) 63.69GB (38.27GB free)
Process Argv --crash-reporter-id bc956f1d-de68-4b79-af0e-b17fb45ba10b
Screen Reader no
VM 0%

Connection to 'wsl+ubuntu' could not be established

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
tftest:31042121
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
vscrpc:30673769
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
945dj816:31013170
pythoncenvptcf:31043158
a69g1124:31046351
dwnewjupytercf:31046870

@chrmarti
Copy link
Owner

This extension doesn't do anything IntelliSense related. Could you double-check? This might be a random pick by the bisect tool.

@chrmarti chrmarti self-assigned this May 15, 2024
@MoonstarCoding
Copy link
Author

This extension doesn't do anything IntelliSense related. Could you double-check? This might be a random pick by the bisect tool.

After bisect found it, I turned it (and only it) off. It has been 2 full days with no issue ever since. It appears this extension stalls the extension host, preventing any of the extensions from working properly.

@chrmarti
Copy link
Owner

Is this when you open a specific source file? Maybe one of the regexes the extension uses is slow on a particular input.

You could also try to get a CPU profile in F1 > Developer: Show Running Extensions and there right-click the Regex extension and Start Extension Host Profile.

@MoonstarCoding
Copy link
Author

Is this when you open a specific source file? Maybe one of the regexes the extension uses is slow on a particular input.

You could also try to get a CPU profile in F1 > Developer: Show Running Extensions and there right-click the Regex extension and Start Extension Host Profile.

To answer point 1: It occurs on any project that has a node_modules folder and more than one TSX file. I couldn't recreate when it was just one though.

To address point 2: due to it having been on my work laptop and crashing the application, I was forced to uninstall it and it is now a black listed plugin for causing this issue reliably on 4 separate work devices. So reinstalling it is not an option. Even if I could, my work network blocks the upload of files with specific extensions, and I have trouble believing one with .cpuprofile would be sanctioned. So I can't help you with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants