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

Parse error when compiling a statement causes memory leak until attachment is disconnected [CORE5646] #5912

Closed
firebird-issue-importer opened this issue Oct 20, 2017 · 4 comments

Comments

@firebird-issue-importer

Submitted by: @asfernandes

Before statement is compiled, a memory pool is created and registered in the attachment.

If statement has error, this pool is only immediatelly destroyed if a request has been created, but statements with syntactic errors does not create requests.

Then the pool is only deallocated at attachment disconnection.

Example statement:

select;

Commits: 9f834ab 5e1b5e1

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

Test works OK, but i can't understand why memory leak can be detected only in even (2nd, 4th, 6th etc) queries to mon$memory_usage (in the version BEFORE this ticket was fixed; i've checked 4.0.0.800)

Sent letter to dimitr, 23.12.2017 22:58

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Oct 20, 2017

Modified by: @asfernandes

assignee: Adriano dos Santos Fernandes [ asfernandes ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 27, 2017

Modified by: @asfernandes

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

resolution: Fixed [ 1 ]

Fix Version: 4.0 Beta 1 [ 10750 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 23, 2017

Modified by: @pavel-zotov

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

QA Status: No test => Done successfully

Test Details: Test works OK, but i can't understand why memory leak can be detected only in even (2nd, 4th, 6th etc) queries to mon$memory_usage (in the version BEFORE this ticket was fixed; i've checked 4.0.0.800)

Sent letter to dimitr, 23.12.2017 22:58

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 23, 2017

Modified by: @pavel-zotov

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants