You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on May 15, 2026. It is now read-only.
Extension crashes VS Code via repeated deletePointsByMultipleFilePaths failures #5516
The extension enters a tight error loop on startup:
Failed to delete points by file paths: Error: Bad Request
at deletePoints
at deletePointsByMultipleFilePaths
at processBatch
Repeats dozens of times in under a second.
Floods the logs and overwhelms the extension host.
Triggers VS Code crash (verified via system and VS Code logs).
🔁 Steps to Reproduce
1. Install the rooveterinaryinc.roo-cline extension.
2. Open a VS Code workspace that includes a directory with many files (e.g. a TypeScript monorepo).
3. Ensure the extension is enabled and VS Code’s telemetry sync is active.
4. Start VS Code and observe:
• Log output (Cmd+Shift+U → Output → Log (Extension Host))
• CPU spikes in Activity Monitor (macOS) or top (CLI)
5. Within seconds, the errors appear repeatedly
6. VS Code slows down and crashes or hangs due to extension host overload.
💥 Outcome Summary
No errors in the VS Code developer console and no crashses
Hi @buck-0x! I'm Dosu and I’m helping the Roo-Code team.
I couldn't find any documentation or known issues about deletePointsByMultipleFilePaths or repeated 'Bad Request' errors causing extension host crashes. There is, however, guidance for handling large projects: try lowering the "File read auto-truncate threshold" in Roo Code's Advanced Settings to reduce resource usage, especially in large workspaces or monorepos. This setting limits how much of each file is read at once and can help prevent overloads in big projects. If the issue persists, you might also try reducing the number of files watched or temporarily disabling telemetry sync to see if that changes the error pattern. There’s a documentation gap here—no official troubleshooting steps for this specific error loop or crash scenario were found. Tips for large projects and resource usage Managing large files and performance
Hey, thank you for reporting this. I took a look and it seems the crash loop is caused by the file watcher's batch processing logic, specifically during calls to deletePointsByMultipleFilePaths in the Qdrant vector store. This triggers repeated "Bad Request" errors that eventually crash the VS Code extension host.
The issue starts when the extension processes a large number of file changes. It tries to delete existing vector embeddings before inserting new ones, but the Qdrant API rejects the delete request, likely due to malformed filters or request size limits. Since the error is re-thrown with no retry logic or backoff, it creates a tight loop that floods the logs and eats CPU until the extension host crashes.
This typically happens on startup because the indexing service runs automatically when the extension activates. In large projects, that immediately kicks off batch processing, which hits the bug.
To fix this, we probably need to:
Add backoff and retry logic for failed Qdrant operations
Limit the number of file paths per request
Handle failures more gracefully so they don't crash the host
Activity
dosubot commentedon Jul 9, 2025
Hi @buck-0x! I'm Dosu and I’m helping the Roo-Code team.
I couldn't find any documentation or known issues about deletePointsByMultipleFilePaths or repeated 'Bad Request' errors causing extension host crashes. There is, however, guidance for handling large projects: try lowering the "File read auto-truncate threshold" in Roo Code's Advanced Settings to reduce resource usage, especially in large workspaces or monorepos. This setting limits how much of each file is read at once and can help prevent overloads in big projects. If the issue persists, you might also try reducing the number of files watched or temporarily disabling telemetry sync to see if that changes the error pattern. There’s a documentation gap here—no official troubleshooting steps for this specific error loop or crash scenario were found.
Tips for large projects and resource usage
Managing large files and performance
To reply, just mention @dosu.
Docs are dead. Just use Dosu.
daniel-lxs commentedon Jul 9, 2025
Hey, thank you for reporting this. I took a look and it seems the crash loop is caused by the file watcher's batch processing logic, specifically during calls to
deletePointsByMultipleFilePathsin the Qdrant vector store. This triggers repeated "Bad Request" errors that eventually crash the VS Code extension host.The issue starts when the extension processes a large number of file changes. It tries to delete existing vector embeddings before inserting new ones, but the Qdrant API rejects the delete request, likely due to malformed filters or request size limits. Since the error is re-thrown with no retry logic or backoff, it creates a tight loop that floods the logs and eats CPU until the extension host crashes.
This typically happens on startup because the indexing service runs automatically when the extension activates. In large projects, that immediately kicks off batch processing, which hits the bug.
To fix this, we probably need to:
niteshbalusu11 commentedon Jul 14, 2025
I am hitting this issue on some of my codebases.