Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Browse database relocated to `/var/tmp` despite settings; quickly consumes all available space under `/`

Ouverte
  • Quelque chose ne va pas ?
#14,795 8 commentaires 1 réaction 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@Colengms y travaille déjà.

Depuis le 25/9/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

bug Language Service more info needed
Environment
  • OS and Version: macOS 26.5.2 (VSCode Editor)
  • VS Code Version: 1.138.0
  • C/C++ Extension Version: 1.34.4
  • If using SSH remote, specify OS of remote machine: Rocky Linux 8.9
Bug Summary and Steps to Reproduce

After updating the C/C++ IntelliSense plugin and VSCode earlier today, I quickly discovered my SSH remote had run out of disk space on /. On investigating, I found a 41GB .browse.VC.db file under /var/tmp/.vscode-cpptools-XXXXXX.

If I delete this file and kill remote cpptools-srv2 instances, the language server restarts, immediately recreates .browse.VC.db, and begins filling the file.

I do see a 70+GB file at the location specified by c_cpp_properties.json (see below), but it appears this configuration setting is no longer being honored. Nor is the path specified by C_Cpp.default.browse.databaseFilename.

This was working until the recent upgrade.

Configuration and Logs
-------- Diagnostics - 9/23/2026, 1:45:49 AM
Version: 1.34.4
Current Configuration:
{
    "name": "Linux",
    "includePath": [
        "<REDACTED>"
    ],
    "defines": [
        "_DEBUG",
        "UNICODE",
        "_UNICODE",
        "NV_LINUX"
    ],
    "compilerPath": "/usr/bin/gcc",
    "cStandard": "c11",
    "cppStandard": "c++17",
    "intelliSenseMode": "linux-gcc-x64",
    "browse": {
        "path": [
            "<REDACTED>"
        ],
        "limitSymbolsToIncludedHeaders": false,
        "databaseFilename": "${workspaceFolder}/.vscode/browse.vc.db"
    },
    "compilerPathIsExplicit": true,
    "cStandardIsExplicit": true,
    "cppStandardIsExplicit": true,
    "intelliSenseModeIsExplicit": true,
    "recursiveIncludesPriorityIsExplicit": false,
    "recursiveIncludesOrderIsExplicit": false,
    "compilerPathInCppPropertiesJson": "/usr/bin/gcc",
    "mergeConfigurations": false,
    "recursiveIncludes": {}
}
Modified Settings:
{
    "C_Cpp.errorSquiggles": "enabled",
    "C_Cpp.default.compilerPath": "/usr/bin/gcc",
    "C_Cpp.default.cStandard": "c11",
    "C_Cpp.default.cppStandard": "c++17",
    "C_Cpp.default.browse.databaseFilename": "/data/vscode-cpptools/${workspaceFolderBasename}/browse.vc.db",
    "C_Cpp.intelliSenseCachePath": "/data/vscode-cpptools"
}
Additional Tracked Settings:
{
    "editorTabSize": 4,
    "editorInsertSpaces": true,
    "editorAutoClosingBrackets": "languageDefined",
    "filesEncoding": "utf8",
    "filesAssociations": {
        "*.c": "c",
        "*.cpp": "cpp",
        "*.h": "c",
        "*.hpp": "cpp"
    },
    "filesExclude": {
        "**/.git": true,
        "**/.svn": true,
        "**/.hg": true,
        "**/.DS_Store": true,
        "**/Thumbs.db": true
    },
    "filesAutoSaveAfterDelay": false,
    "editorInlayHintsEnabled": true,
    "editorParameterHintsEnabled": true,
    "searchExclude": {
        "**/node_modules": true,
        "**/bower_components": true,
        "**/*.code-search": true
    },
    "workbenchSettingsEditor": "ui"
}
cpptools version (native): 1.34.3.0
Current database path: /var/tmp/.vscode-cpptools-102571/browse-database/{16150885415521154784}/.browse.VC.db
No active translation units.
Other Extensions

No response

Additional context

No response

Langage dominant
TypeScript
Étoiles
6.2k
Forks
1.7k
Merge moyen
1 j 22 h
PR mergées (30 j)
35

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de microsoft/vscode-cpptools

Toutes les issues de microsoft/vscode-cpptools

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.