You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
The text was updated successfully, but these errors were encountered: