microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
162.66k stars 28.68k forks source link

VSIX Files Adding To /tmp Each Hour VSCode is Open. #76911

Closed vindicatorr closed 5 years ago

vindicatorr commented 5 years ago

Issue Type: Bug

Steps to Reproduce:

  1. Open Visual Studio Code.
  2. Monitor /tmp folder for created vsix files.

Does this issue occur when all extensions are disabled?: No

I am already aware of: https://github.com/Microsoft/vscode/issues/53110 and https://github.com/microsoft/vscode/issues/54925 both of which are closed with no apparent resolution after about 1 year so far. In other words don't close this, or re-open 53110, or let me know if this issue should be posted to vscode-cpptools instead ("why" below).

Each hour that vscode is open, a vsix is downloaded and is never removed from /tmp. I unzipped 2 of the 20+ vsix files and it looks to be related to the c/cpp extension. This is the "why" it MAY need to be posted to their repository instead of here. Given that Archlinux mounts /tmp as tmpfs, that is taking up memory, and it adds up over hours. I do NOT believe it's related to https://github.com/microsoft/vscode-cpptools/issues/3093 since I'm online and it has no problems installing and I have no problems when using it. I usually only update if a changelog looks appealing to me or applicable to an issue I have.

extensions.autoCheckUpdates is set to "enabled". Wouldn't this ONLY check for a version online and NOT download the updated extension?

Extensions: Auto Update is set to "disabled". So it shouldn't even be downloading the extension automatically.

Expectations:

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz (4 x 2574)| |GPU Status|2d_canvas: enabled
flash_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)|1, 1, 1| |Memory (System)|7.25GB (2.50GB free)| |Process Argv|| |Screen Reader|no| |VM|0%|
Extensions (19) Extension|Author (truncated)|Version ---|---|--- html-snippets|abu|0.2.1 Doxygen|bbe|1.0.0 arm|dan|0.3.0 xml|Dot|2.4.0 vscode-solution-explorer|fer|0.3.1 ilspy-vscode|ics|0.7.5 vscode-nuget-package-manager|jmr|1.1.6 cortex-debug|mar|0.3.0 cortex-debug-dp-stm32f1|mar|1.0.0 cortex-debug-dp-stm32f4|mar|1.0.0 mssql|ms-|1.5.0 cpptools|ms-|0.23.1 csharp|ms-|1.20.0 debugger-for-chrome|msj|4.11.3 view-in-browser|qin|0.0.5 msbuild-project-tools|tin|0.2.54 debug|web|0.23.1 riscv|zhw|0.0.4 linkerscript|Zix|1.0.0
sandy081 commented 5 years ago

@vindicatorr VSIX files are downloaded to /tmp folder from Marketplace and will be deleted after installing. Fix for #53110 does this.

Can you please let us know which vsixs are those? Can you reproduce this issue by disabling all extensions? Is it possible that one of the installed extensions is doing this?

vindicatorr commented 5 years ago

I'll just copy/paste what I had already filled in for the bug template:

"Does this issue occur when all extensions are disabled?: No" "I unzipped 2 of the 20+ vsix files and it looks to be related to the c/cpp extension"

I've attached one of the vsix files (had to add .zip to be uploaded here): tmp-3523lOiS2uBxUhQ.vsix.zip

sandy081 commented 5 years ago

I remember there is beta feature in C++ extension that makes it to download the VSIX.

I can confirm that when VS Code installs extension from Marketplace, it downloads the VSIX into temp location and deletes it after installing.

Can you please file issue against C++ extension asking them if they are deleting the VSIX after downloading.

vscodebot[bot] commented 5 years ago

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!