Use case or problem
I have a few quite large files in my vault (largest is 1.6m characters), and when I try to use the Core Search Plugin, it often hangs a bit trying to find and display all results. This is understandable.
However, if I don’t type fast enough, it can happen that the plugin searches my entire vault for a single letter and freezes up for 30 seconds to build the list of the results, using 3GB of RAM (example: searching “a”).
Proposed solution
Add an optional limit to the number of results that are displayed when using the Core Search Plugin. The search itself is very fast (as expected), the main problem is the number of results and Obsidian having to render them all.
It doesn’t happen often that a user scrolls through more than 10k results without refining their query, so a default around 10k would most likely be more than enough. In the off-chance that they actually do want to continue scrolling, adding a button to load more results would likely solve that problem.
However, I personally would be fine with just a single setting that defaults to loading all results and just having the ability to stop my computer from freezing by limiting it manually to around 1k.