Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.3.1, 3.4.0
Description
We noticed a possible resource leak here. The call to close on storage at line 267 can throw an exception. If it occurs, then committedTxnId and curSegment are never closed.
I'll submit a pull request to fix it.
Attachments
Issue Links
- links to