Closed Alkaid-Benetnash closed 3 weeks ago
@Alkaid-Benetnash Those are temp files created by the EDG parser we use. From looking at the code, it looks like you can change the location by setting the TMPDIR environment variable, but I haven't tested that.
Thanks for checking the source code. Is that part open sourced? I tried to figure this out myself but couldn't find the EDG related code.
I can also confirm that the TMPDIR
env works. Maybe it is better to let the EDG parser follow the intellisense cache dir config. But I am happy with this answer and it should be a good enough workaround for other users who come across this issue.
Feel free to close this.
Same issue, using VSCode remote/SSH with Windows10 local / Redhat Linux (7.x & 8.x) remote. /tmp directory on remote Linux server fills with edg0_XXXX files which are not removed when the local VSCode instance is stopped.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
cpptools- 6287 brozek DEL REG 253,4 535 /tmp/edg0_6287
cpptools- 6287 brozek 11u REG 253,4 1335726081 535 /tmp/edg0_6287 (deleted)
This feature request is being closed due to insufficient upvotes. Please leave a 👍-upvote or 👎-downvote reaction on the issue to help us prioritize it. When enough upvotes are received, this issue will be eligible for our backlog.
Environment
"Help->About" copied from VSCode
Bug Summary and Steps to Reproduce
Bug Summary: Basically the same as #3633 . A good summary is in https://github.com/microsoft/vscode-cpptools/issues/3633#issuecomment-523682322 Basically there is no way to configure where to store the
tmp/edg
cache files. And those files can be huge and occupying spaces depending on how the/tmp
is mounted.Steps to reproduce:
lsof /tmp
tmpfs
). Those files are opened by cpptools-srv/tmp/edg0_${PID}
locations. Note that theC_Cpp.intelliSenseCachePath
is not "/tmp", so the edg0 caches are not controlled by this option.Expected behavior: Either properly close the deleted/unlinked cache file, or give users an option to use another directory for the edg0 cache.
Another workaround to use mount namespaces to let vscode to use a special
/tmp
dir. Example:Configuration and Logs
c_cpp_log_diagnostics.log c_cpp_language_server_debug.log