Skip to content

Fixing memory leaks observed in ASan (#4690)#4692

Merged
tanscorpio7 merged 4 commits intobabelfish-for-postgresql:BABEL_4_X_DEVfrom
amazon-aurora:babel-6422-4x
Apr 2, 2026
Merged

Fixing memory leaks observed in ASan (#4690)#4692
tanscorpio7 merged 4 commits intobabelfish-for-postgresql:BABEL_4_X_DEVfrom
amazon-aurora:babel-6422-4x

Conversation

@harshdubey166
Copy link
Copy Markdown
Contributor

Cherry-pick of #4690

This commit fixes memory leaks observed when testing with ASan

  1. In the function PrepareRowDescription() , strdup() allocates memory using the system's malloc(), which is completely outside PostgreSQL's memory management. This means the string stored in relMetaDataInfo->partName[1] lives in malloc-heap, not in any PostgreSQL memory context. By using pstrdup() , it allocates using palloc() inside the current memory context (MessageContext), so it's properly tracked and will be freed when that context is destroyed.

  2. Similarly in the function rewrite_if_condition(), strdup uses malloc which is invisible to PostgreSQL's memory management while pstrdup allocates in the current memory context, which gets cleaned up automatically.

Task: BABEL-6422

Authored by : harshdu@amazon.com
Signed-off by : harshdu@amazon.com

Check List

  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.

For more information on following Developer Certificate of Origin and signing off your commits, please check here.

harshdubey166 and others added 4 commits April 2, 2026 06:51
This commit fixes memory leaks observed when testing with ASan

1. In the function TdsSendRowDescription() , strdup() allocates memory using the system's malloc(), which is completely outside PostgreSQL's memory management. This means the string stored in relMetaDataInfo->partName[1] lives in malloc-heap, not in any PostgreSQL memory context.
By using pstrdup() , it allocates using palloc() inside the current memory context (MessageContext), so it's properly tracked and will be freed when that context is destroyed.

2. Similarly in the function rewrite_if_condition(), strdup uses malloc which is invisible to PostgreSQL's memory management while pstrdup allocates in the current memory context, which gets cleaned up automatically.

Task: BABEL-6422

Authored by : harshdu@amazon.com
Signed-off-by: Harsh Dubey <harshdu@amazon.com>
Signed-off-by: Harsh Dubey <harshdu@amazon.com>
@tanscorpio7 tanscorpio7 merged commit 382bede into babelfish-for-postgresql:BABEL_4_X_DEV Apr 2, 2026
48 checks passed
@tanscorpio7 tanscorpio7 deleted the babel-6422-4x branch April 2, 2026 10:10
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