Skip to content

Fix memory leak in Query Processor and ProxySQL_Admin::flush_pgsql_variables___database_to_runtime #5037

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

Open
wants to merge 2 commits into
base: v3.0
Choose a base branch
from

Conversation

rahim-kanji
Copy link
Collaborator

Addresses memory leaks in Query Processing and in ProxySQL_Admin::flush_pgsql_variables___database_to_runtime

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @rahim-kanji, 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 critical memory leaks identified in two key areas of the system: the Query Processor's rule management and the ProxySQL_Admin's PostgreSQL variable flushing mechanism. The changes ensure that dynamically allocated memory is properly released, improving the application's stability and resource utilization.

Highlights

  • Query Processor Memory Management: Ensured proper deallocation of client_addr and proxy_addr fields within QP_rule_t structures by adding free calls in the __delete_query_rule function (lines 132-134).
  • Admin Variable Flush Memory Management: Removed an unnecessary get_variable_string call and its associated assert in ProxySQL_Admin::flush_pgsql_variables___database_to_runtime (lines 741-742 removed), which was likely causing a memory leak by not freeing the returned string.
Using Gemini Code Assist

The 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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and 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 to provide feedback.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a 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 addresses two memory leaks, one in the query processor and another in the admin variable flushing logic. The changes are straightforward and correct:

  1. In lib/Query_Processor.cpp, missing free() calls for client_addr and proxy_addr in __delete_query_rule have been added, preventing a memory leak when query rules are deleted or reloaded.
  2. In lib/Admin_FlushVariables.cpp, an unused variable previous_default_client_encoding was being allocated but never freed. The removal of this variable correctly plugs the leak.

Both changes are well-targeted and effectively resolve the described memory leak issues. The code quality is maintained, and the fixes are consistent with the existing memory management patterns in the codebase. This is a good contribution to improving the stability of the application.

@rahim-kanji rahim-kanji changed the title Fix memory leak in Query Processor Fix memory leak in Query Processor and ProxySQL_Admin::flush_pgsql_variables___database_to_runtime Jul 8, 2025
@renecannao
Copy link
Contributor

Can one of the admins verify this patch?

@renecannao
Copy link
Contributor

add to whitelist

Copy link

sonarqubecloud bot commented Jul 8, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants