OOM when running indexer

[Fusion]

App Version

v3.23.8

API Provider

Google Gemini

Model Used

text-embedding-004

Roo Code Task Links (Optional)

Running out of memory pretty quickly after I clicked the "Index" button. Could be due to an issue with Swift language.

🔁 Steps to Reproduce

In the "Codebase Indexing" dialog, I do not touch the advanced options.
I set it up to use a self-hosted qdrant server.

I try to index a codebase that is a mix of Swift and Go code (and a little bit of C)

💥 Outcome Summary

Here is some console goodness.
First, a complaint about Swift:

repeated once.

quickly followed by:

📄 Relevant Logs or Errors (Optional)

[dosubot]

Hi @Fusion! I'm Dosu and I’m helping the Roo-Code team.

There are a few things that could be causing the OOM error during indexing. Roo Code has a 1MB per-file limit for indexing, and best results come from languages supported by Tree-sitter parsers—Swift support depends on parser compatibility, which can sometimes cause issues if the parser version is mismatched or incomplete. If the Swift parser fails to load, it could cause memory issues, especially if the indexer tries to process large or unsupported files repeatedly or inefficiently.

You can try lowering the "Maximum Concurrent Files" setting (found in Advanced Settings → Context Management → "Concurrent file reads limit") to reduce memory usage during indexing. Also, make sure your .gitignore and .rooignore files exclude any large directories or files that don't need to be indexed, as large codebases or files can quickly exhaust memory resources. Roo Code chunks files into small pieces for embedding, but inefficient chunking or unsupported language features can still cause problems, especially with mixed-language projects or large Swift files.

There are no documented OOM issues specific to the Google Gemini model or self-hosted Qdrant, and no existing tickets or docs directly address this exact scenario. If the issue persists after adjusting concurrency and ignores, it may be related to Swift parser compatibility or a memory leak in the extension host. You can find more details on these limitations and settings in the docs:

• Indexing limitations and language support
• Concurrent file reads setting
• Swift parser/tool limitations

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}