Full RAM usage leads to crash PC

[vmd666666-sketch]

Hey i use it as Code navigation, but my projects starts to being so big, sometime i use to search some logs, it runs out my 64gb RAM to the fullest and leads to crash my PC. Setted some guardrails in the code, but didn't work. It not happen during indexing, but on search mode.

[starkmarkus]

This sounds like a search-time memory blowup rather than an indexing problem, which is an important distinction.

If the crash happens when searching logs or very large generated files, I would first exclude those files from the indexed/searchable project. Large log files, build artifacts, vendored dependencies, minified bundles, generated code, and cache folders can make search mode much more expensive than normal code navigation.

Things I would check first:

1. Does it happen with every search query, or only broad queries?
2. Does it happen only when searching log files?
3. How large is the repository and the .gitnexus directory?
4. Are node_modules, dist, build, target, .venv, logs, coverage, vendor, etc. excluded?
5. Does the same search work after removing logs/generated files from the indexed scope?

As a workaround, I would try re-indexing after excluding non-source files, especially logs:

logs/
*.log
*.out
*.tmp
node_modules/
dist/
build/
target/
coverage/
.venv/
vendor/

If GitNexus supports a project ignore file such as .gitnexusignore or respects .gitignore, put these patterns there and rebuild the index. If it does not currently support excluding files from search mode, that would be a very useful feature request.

From a product side, search mode should probably have hard guardrails too, for example:

• max files scanned per query
• max file size searched
• max result count
• streaming / paginated search results
• memory cap with graceful error instead of exhausting RAM
• option to exclude logs/generated files from search

A 64 GB machine should not become unresponsive from one search query, even on a large project. The app should stop the query or return a clear “query too broad / too many files” error before the OS runs out of memory.

For a useful bug report, it would help to include:

• GitNexus version
• OS
• Node version
• approximate repo size / file count
• size of .gitnexus/
• example search query that triggers the crash
• whether logs/generated files are included
• memory usage pattern if you can capture it

My guess is that the search path is loading or materializing too many matches/files into memory at once. Excluding logs and generated files is the best workaround, but GitNexus probably also needs a search-time memory limit so this fails safely instead of crashing the whole PC.