You are right, thank you for letting me know.
I will give your mitigations a try
/etc/gromox/midb.cfg:midb_cache_interval=5minutes
/etc/gromox/midb.cfg:midb_reload_interval=10minutes
@crpb maybe you could ask the developers to do a "bisect" with their sourcecode?
my last known good was 2.29-20 (for aarch64) on Stable.
A bisect should find the culprit quite quickly.
... and since you mentioned in the other post, that you already had the issue with 2.30-21, there really should not be too many commits.
