smb: post-GAP some transactions never close
In long running flows with lots of transactions and at least one GAP, transactions started prior to the GAP could be left open. This could lead to the tx list getting longer and longer. This in turn would lead to high CPU use and higher than expected memory use.
Updated by Victor Julien almost 4 years ago
- Status changed from Assigned to Closed