Binary data can trigger a cpptools infinite loop

Aperta
#14,723 4 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@sean-mcmanus ci sta già lavorando.

Dal 1/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

bug Language Service more info needed
Environment
  • OS and Version: MacOS 26, using a container running Ubuntu 24.04.4 LTS
  • VS Code Version: 1.135.0 (Universal)
  • C/C++ Extension Version: 0.6.18
  • If using SSH remote, specify OS of remote machine:
Bug Summary and Steps to Reproduce

Bug Summary:

I have a file that, when placed in a directory within a workspace that uses cpptools, causes cpptools-srv2 to get stuck in an apparent infinite loop. I've redacted the file so that it's mostly NULs. In fact, strings things it has no text at all.

Steps to reproduce:

  1. Make sure that the C++ extension is installed.
  2. Extract the attached file. Name it testfile (or probably just about anything else).
  3. Check your CPU usage.

I believe this is not a security issue with any meaningful impact, as (as far as I know) it's only triggerable by placing the offending content into a non-restricted-mode workspace, and it's straightforward to get actual code execution in this context using ordinary configuration. It is, however, a kind of annoying functionality bug, since I have repeatedly triggered it by accident.

testfile.gz

FWIW, there is very little content in that file. I managed to reduce it to a file that's kind of large but has almost as little complexity as one could imagine. I did not try to reduce it to a smaller file.

Configuration and Logs
There is no relevant configuration.  The log says:


LSP: (received) cpptools/fileCreated: file:///workspaces/master/testfile
LSP: (invoked) cpptools/fileCreated: file:///workspaces/master/testfile
Initiating store rescan...
Other Extensions

No response

Additional context

No response

Lingua principale
TypeScript
Stelle
6.2k
Fork
1.7k
Merge medio
14h 46m
PR unite (30g)
61

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/vscode-cpptools

Tutte le issue di microsoft/vscode-cpptools

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.