Skip to content
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

Memory leak in GBAK code when used as service [CORE5899] #6157

Closed
firebird-issue-importer opened this issue Aug 22, 2018 · 3 comments
Closed

Comments

@firebird-issue-importer

Submitted by: @AlexPeshkoff

Small memory leak (about few hundreds of bytes per call) takes place in gbak when it's invoked as service inside engine

Commits: c68bfdb 3831b18

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Aug 22, 2018

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Aug 22, 2018

Commented by: @AlexPeshkoff

Instead linear list of allocated memory always allocate it directly from the pool creating separate pool for gbak when used as service. Memory leaks are prevented in this case due to delete-by-pool.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Aug 22, 2018

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 4.0 Beta 1 [ 10750 ]

Fix Version: 3.0.4 [ 10863 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment