Fix two memory leaks on SQLite3 prepared statements - Closes #4491 #4504
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The leaks are exercised during table regeneration at 'MySQL_HostGroups_Manager::commit'.
JavierJF
changed the title
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes two memory leaks that are exercised during tables regeneration due to servers reconfiguration.
Details
Leaks are reflected in the amount of memory used by
SQLite3. Leaks are small and will only affect environments with high frequency servers reconfiguration, the number of servers isn't relevant.This PR also motivated PR #4506, which enables accumulative profile dumps for
jemalloc.Affected versions
mysql_hostgroup_attributes: Since2.5.0.mysql_servers_ssl_params: Since2.6.0.