Skip to content

s3: workaround on-reload memleak when no role is set#318

Merged
alltilla merged 1 commit intoaxoflow:mainfrom
orymate:s3-memleak-workaround
Oct 2, 2024
Merged

s3: workaround on-reload memleak when no role is set#318
alltilla merged 1 commit intoaxoflow:mainfrom
orymate:s3-memleak-workaround

Conversation

@orymate
Copy link
Member

@orymate orymate commented Oct 1, 2024

AxoSyslog leaks an amount of memory every time it's reloaded if an s3
destination is configured (#317). As a quick workaround we partially revert the
patch introducing the use of boto3.Session when no role() is set.

Copy link
Member

@alltilla alltilla left a comment

Choose a reason for hiding this comment

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

Thanks for the fix! :)

Please git commit --amend -s. Otherwise approve.

AxoSyslog leaks an amount of memory every time it's reloaded if an s3
destination is configured. As a quick workaround we partially revert the
patch introducing the use of `boto3.Session` when no `role()` is set.

Signed-off-by: Mate Ory <[email protected]>
@orymate orymate force-pushed the s3-memleak-workaround branch from 22f143a to 8215551 Compare October 1, 2024 11:33
@orymate orymate marked this pull request as ready for review October 2, 2024 07:32
@orymate orymate requested a review from alltilla October 2, 2024 07:36
@pepov
Copy link
Member

pepov commented Oct 2, 2024

A comment would probably be worth to explain the scenario when a session could leak memory in case of frequent reloads.

@alltilla alltilla merged commit 89ba587 into axoflow:main Oct 2, 2024
alltilla added a commit to alltilla/axosyslog that referenced this pull request Oct 2, 2024
Signed-off-by: Attila Szakacs <[email protected]>
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.

3 participants