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

Possible memory leak in WITH RECURSIVE query [CORE2311] #2735

Closed
firebird-automations opened this issue Feb 8, 2009 · 7 comments
Closed

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @hvlad

If some recursive member used indexed (rsb_indexed) or navigational (rsb_navigate) access path then memory leak is possible.
Memory leaked from request's pool therefore it is visible if some prepared statement executed many times.
Also it is visible if procedure or trigger used recursive query.

Commits: 697e967 0950f99

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

One need to query mon$memory_usage before and after such query, but mon$ tables did appear in 2.5.0 and this ticket was already fixed in 2.5 BETA 1.

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

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

resolution: Fixed [ 1 ]

Fix Version: 2.5 Beta 1 [ 10251 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Fix is backported into 2.1.3

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Fix Version: 2.1.3 [ 10302 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: No test => Cannot be tested

Test Details: One need to query mon$memory_usage before and after such query, but mon$ tables did appear in 2.5.0 and this ticket was already fixed in 2.5 BETA 1.

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