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
There's a memory leak in the log procedure of the logger_pkg. A string is allocated in get_location, but not released. When I add a deallocate before the end of the procedure, the problem disappears:
-- Count even if disabled
count_log(logger, log_level);
endif;
deallocate(location.file_name);
endprocedure;
Since this function is indirectly called even for passing checks, the memory consumption can quickly get out of hand: Several of my testcases devour several GiB of RAM after running for a few minutes.
The text was updated successfully, but these errors were encountered:
There's a memory leak in the
log
procedure of thelogger_pkg
. A string is allocated inget_location
, but not released. When I add adeallocate
before the end of the procedure, the problem disappears:Since this function is indirectly called even for passing checks, the memory consumption can quickly get out of hand: Several of my testcases devour several GiB of RAM after running for a few minutes.
The text was updated successfully, but these errors were encountered: