-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leak during internal object listing #2264
Conversation
- Happens when the Skip algorithms tells the function to skip an entry. - In this case, we recursively call the internalListObject function. - However, we never properly close the stream created from the Transform object, that requires specific cleanup. - Overall, the logic is too complex, so cleaning is now centralized and modular, so we clean anything that is still there. Issue: ARSN-437
Hello williamlardier,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
To avoid missing code paths where some sockets are not properly cleaned, we now clean each of them when calling cbOnce, to ensure the logic is called once per function (or recursive) call. Issue: BB-602
13b03d1
to
21210d3
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## development/8.1 #2264 +/- ##
===================================================
+ Coverage 64.84% 64.90% +0.06%
===================================================
Files 215 215
Lines 17287 17298 +11
Branches 3535 3514 -21
===================================================
+ Hits 11209 11228 +19
+ Misses 6063 6055 -8
Partials 15 15 ☔ View full report in Codecov by Sentry. |
143e999
to
8daf4a2
Compare
A specific case, before calling recursively the function, require a cleanup of the resources. Issue: BB-602
Issue: ARSN-437
8daf4a2
to
94c7038
Compare
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command:
Alternatively, the |
/create_integration_branches |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
/approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue ARSN-437. Goodbye williamlardier. The following options are set: approve, create_integration_branches |
Issue: ARSN-437
For reference, some tests were started to automate memory leak detection, but not very stable so far, or require to run it for long times: https://github.com/scality/Arsenal/compare/bugfix/ARSN-437-ballooning?expand=1