It's a feature, not a bug :D
The cool thing about that is that it is the OS that will get to choose which process to allocate memory, and you can always run it somewhere with less memory available, and it will work the same way
But your OS will share the Meilisearch memory with other process seamlessly, you don’t have anything to do. In htop it’s the yellow bar, and it’s basically a big cache shared between all processes.
This is a trick I learned years ago with other mmap-based systems.
What was your strategy to measure that?
* Meili uses 50% RAM
* I use 10-20% with another script to occasionally index new data
* When indexing, Meili could jump to use 70-80% RAM
* Meili is OOM killed
While Meilisearch is capable of limiting it's resident (actual mallocs) memory. However, it requires a bare minimum (about 1GiB).