We had an issue where cross-receiver message settlement caused a memory leak as entries in the unsettledMessages map weren't deleted. While this has been fixed, it brings up the question of whether unsettledMessages really needs to be a map or just an atomically accessed count.
We had an issue where cross-receiver message settlement caused a memory leak as entries in the
unsettledMessages
map weren't deleted. While this has been fixed, it brings up the question of whetherunsettledMessages
really needs to be a map or just an atomically accessed count.