Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#14,795 8 Kommentare 1 Reaktion 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@Colengms arbeitet bereits daran.

Seit 25.9.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

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

Vorherrschende Sprache
TypeScript
Sterne
6.2k
Forks
1.7k
Ø Merge
1 T. 21 Std.
Gemergte PRs (30 T.)
36

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/vscode-cpptools

Alle Issues in microsoft/vscode-cpptools

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.