Hi @lucota90! Thanks for the report
Right now the indexer runs fully in memory and doesn’t persist anything to disk, so after a crash or editor restart it will start indexing from scratch. That’s expected behavior for now.
Because of this, it’s possible you’re hitting system memory limits during indexing.
To help narrow this down and rule out any other issues, could you share:
From my side, I’ll also look into making the indexer handle low memory situations gracefully. In those cases, it might not be able to index or return everything, but it should at least avoid crashing and still provide partial results.
I’m also considering adding more control over what gets indexed, so large projects can skip or limit certain data through advanced settings, or define a fixed memory budget for the indexer, similar to how Rider handles it.
I don’t have an immediate fix yet, but this is something I’ll prioritize for the next update.
Additional Context
I just tested this on my side using a mid-to-large project:
-
~200k lines of C++
-
Hundreds of Blueprints
I measured the editor’s memory usage:
So in this case, the indexer adds roughly +3.4 GB of RAM usage on top of the engine.
My machine has 128 GB of RAM, so I don’t hit memory limits during indexing. However, this does highlight that the plugin can become quite memory intensive, especially on larger or more complex projects.
If your project is significantly bigger, or your available RAM is lower, currently it’s possible to run into out of memory crashes.
