If you can reproduce it with current versions, I would suggest to file
an issue on https://github.com/rabbitmq/rabbitmq-server/issues/

The behavior you describe seems to match
https://github.com/rabbitmq/rabbitmq-server/issues/1873 but the
maintainers seem to think it's been fixed by a number of
somewhat-related changes in 3.7.13, because nobody reported issues
anymore :)