Closed MattyRad closed 5 years ago
I'm not 100% sure of the exact steps it would take to reproduce the error, I just know I installed the plugin and was unable to change my settings in the Settings UI afterwards. If it's not obvious what the issue is, feel free to close this, I can go without.
If it helps, I've experienced a very similar issue with Firefox in Ubuntu Linux (https://bugzilla.mozilla.org/show_bug.cgi?id=1451466).
Ok, I think I found what I changed that caused this. I changed the "Max Lines" config from 9999 to 300. Changing the value back to 9999 seems to have fixed the issue. I also ran vscode from the command line without with --unity-launch
flag which may have affected/improved the state of vscode on my machine. I don't exactly know what fixed it, but it appears to work now.
Issue Type: Bug
Extension version: 0.0.20 VS Code version: Code 1.36.1 (2213894ea0415ee8c85c5eea0d0ff81ecc191529, 2019-07-08T22:55:08.091Z) OS version: Linux x64 4.18.0-25-generic
System Info
|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 2400)| |GPU Status|2d_canvas: enabledflash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: disabled_software
skia_deferred_display_list: disabled_off
skia_renderer: disabled_off
surface_synchronization: enabled_on
video_decode: unavailable_off
viz_display_compositor: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|3, 2, 2| |Memory (System)|7.56GB (0.43GB free)| |Process Argv|--unity-launch| |Screen Reader|no| |VM|0%|