This was a real regression in the 0.50 line, not a config problem. The Metabase team traced the OOMs to a thread leak and fixed it in PR #45253, which shipped in the 0.50.7+ releases; the maintainers asked everyone on the thread to upgrade to 0.50.7 and then closed the issue once the fix was out. So…
This was a real regression in the 0.50 line, not a config problem. The Metabase team traced the OOMs to a thread leak and fixed it in PR #45253, which shipped in the 0.50.7+ releases; the maintainers asked everyone on the thread to upgrade to 0.50.7 and then closed the issue once the fix was out. So…