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 with some statements and expressions [CORE6331] #6572

Closed
firebird-issue-importer opened this issue Jun 11, 2020 · 4 comments
Closed

Comments

@firebird-issue-importer

Submitted by: @asfernandes

Some statements and expressions (window function, new aggreate functions, savepoint) are allocated from the global pool instead from the statement pool and are never deallocated.

Commits: 8f78297 98054a2

====== Test Details ======

It seems that the way to see the leak is via OS memory usage of the process.
Letter from Adriano, 16.06.2020 13:54.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jun 11, 2020

Modified by: @asfernandes

assignee: Adriano dos Santos Fernandes [ asfernandes ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jun 12, 2020

Modified by: @asfernandes

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

resolution: Fixed [ 1 ]

Fix Version: 3.0.6 [ 10889 ]

Fix Version: 4.0 RC 1 [ 10930 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jun 15, 2020

Modified by: @pavel-zotov

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

QA Status: No test => Not enough information

Test Details: Any suggestion will be appreciated. Sent letter to Adriano. Waiting for reply.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jun 18, 2020

Modified by: @pavel-zotov

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

QA Status: Not enough information => Deferred

Test Details: Any suggestion will be appreciated. Sent letter to Adriano. Waiting for reply. => It seems that the way to see the leak is via OS memory usage of the process.
Letter from Adriano, 16.06.2020 13:54.

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