-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Open
Labels
bughelp wantedCan be fixed in the public (open source) repo.Can be fixed in the public (open source) repo.not reproingWe're not able to reproduce the issue (it's unlikely to get fixed until we find one).We're not able to reproduce the issue (it's unlikely to get fixed until we find one).tasks/build/debugAn issue relating to tasks.json (e.g. build issues)An issue relating to tasks.json (e.g. build issues)
Description
Environment
- OS and Version: Windows 11 Pro 10.0.22621
- VS Code Version: 1.75.0
- C/C++ Extension Version: 1.14.1
- If using SSH remote, specify OS of remote machine: N/A
Bug Summary and Steps to Reproduce
Bug Summary:
Issuing the build command (Ctrl+B) may sometimes cause VSCode to spend 5-10 seconds "Fetching Build Tasks..." (in status bar) before showing the build tasks menu. I've narrowed down the culprit to the CppTools extension and its C/C++ task provider that suggests a task depending on the file type, aka "detected tasks" in the build menu. I was able to fix this issue by changing the "Task: Auto Detect" setting to "off".
Steps to reproduce:
- Open a workspace/folder with a C/C++ file.
- Press Ctrl+B and wait for the menu to show.
- If menu shows immediately, press escape.
- Repeat steps 2-3 until you see "Fetching Build Tasks..." in the status bar.
Expected behavior:
There shouldn't be any wait for the build tasks menu to show, especially after its already been shown once before. It should be instantaneous.
Configuration and Logs
No response
Other Extensions
No response
Additional context
No response
Metadata
Metadata
Assignees
Labels
bughelp wantedCan be fixed in the public (open source) repo.Can be fixed in the public (open source) repo.not reproingWe're not able to reproduce the issue (it's unlikely to get fixed until we find one).We're not able to reproduce the issue (it's unlikely to get fixed until we find one).tasks/build/debugAn issue relating to tasks.json (e.g. build issues)An issue relating to tasks.json (e.g. build issues)