Parse error when compiling a statement causes memory leak until attachment is disconnected [CORE5646] #5912
Assignees
Comments
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 1 [ 10750 ] |
Modified by: @pavel-zotovstatus: 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 |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: