If MaxScale is configured with query_classifier_cache_size=0 and there are many short connections to the service, the MaxScale instance appears to leak memory. This goes on until the process is killed by the OOM killer.

So far there's been no way to reproduce this outside of the system in question and the number one theory at this point is memory fragmentation that happens somewhere in the SQLite library.