We’ve just released NServiceBus 7.1.10, and 6.5.8.
This patch release fixes a memory leak in the in memory gateway deduplication persistence which can result in endpoints to allocate excessive amounts of RAM or even crash due to
Automatic restarts is not a good workaround for this issue as during a restart all the deduplication data is lost and gateway channel is vulnerable to duplicate message processing.
Note: The bug also occurs in NServiceBus 5.x but this package is out of mainstream support. The workaround is to upgrade to 6.x or newer. If upgrading is not possible, contact Particular about extended support.
- #3564 Memory leak in in-memory gateway persistence caused by not cleaning up deduplication records.
How to know if you are affected
Customers that use the Gateway and use In-Memory persistence are affected.
- The process consumes large amounts of RAM (250MB+)
- OutOfMemoryExceptions are experienced
Should you upgrade immediately
Upgrade immediately if you noticed above symptoms. Otherwise, upgrade during the next maintenance window.
Where to get it
You can download the updated version directly from NuGet: https://www.nuget.org/packages/NServiceBus/
The team in Particular