-
Notifications
You must be signed in to change notification settings - Fork 5k
Fix/fixMemleak336 #33261
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
Fix/fixMemleak336 #33261
Conversation
Summary of ChangesHello @yihaoDeng, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses a memory leak, identified as '336', by implementing more rigorous resource management within the transport layer. The changes focus on ensuring proper cleanup of client request contexts and preventing dangling pointers after context merging, thereby improving the overall stability and memory efficiency of the system. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request appears to fix a memory leak by ensuring userCtx is cleaned up in notifyExceptCb and by nullifying pointers in transCtxMerge after cleanup to prevent dangling pointers. The changes are generally good. I've suggested a small refactoring in transCli.c to reduce code duplication and improve readability.
| if (code != 0) { | ||
| freeUserCtx(pReq); | ||
| destroyReq(pReq); | ||
| return code; | ||
| } | ||
| pInst->cfp(pInst->parent, pResp, NULL); | ||
|
|
||
| freeUserCtx(pReq); | ||
| destroyReq(pReq); | ||
| return code; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The calls to freeUserCtx(pReq) and destroyReq(pReq) are duplicated in both the success and error paths. You can refactor this to remove the duplication, which will make the code cleaner and easier to maintain.
if (code == 0) {
pInst->cfp(pInst->parent, pResp, NULL);
}
freeUserCtx(pReq);
destroyReq(pReq);
return code;
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 3.3.6 #33261 +/- ##
========================================
Coverage ? 57.01%
========================================
Files ? 431
Lines ? 261376
Branches ? 92102
========================================
Hits ? 149026
Misses ? 61002
Partials ? 51348
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
|
Description
Please briefly describe the code changes in this pull request.
Checklist
Please check the items in the checklist if applicable.