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
Memory leak in FB2.5 trace plugin [CORE2934] #3317
Comments
Modified by: Denis Nosov (dens256)security: Developers [ 10012 ] => |
Commented by: @hvlad Can't reproduce. Are you sure you used fresh snapshot build ? There was few memory leaks fixed recently |
Commented by: @dyemanov I cannot reproduce it either (build 2.5.0.25958 on Windows 7, SuperClassic mode). |
Commented by: Denis Nosov (dens256) I rechecked. For reproduce add line in firebird.conf: fbtrace.conf is default (from snapshot build). Memory leak occurs not only on SuperClassic, but also on SuperServer. |
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Commented by: @hvlad Better reflect nature of bug |
Modified by: @hvladVersion: 2.5 RC1 [ 10362 ] Version: 2.5 Beta 2 [ 10300 ] Version: 2.5 Beta 1 [ 10251 ] summary: Memory leak in FB2.5 SuperClassic => Memory leak in FB2.5 trace plugin |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 RC3 [ 10381 ] Fix Version: 3.0 Alpha 1 [ 10331 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Denis Nosov (dens256)
When connecting / disconnecting, not all memory is freed. After a few thousand connections memory ends and the server process crashed.
_input.sql:
select count(*) from rdb$database;
exit;
test.bat:
@echo off
:mc
isql -u SYSDBA -p masterke -i _input.sql -o _output.txt "localhost:d:\Program Files\Firebird\Firebird_2_5\examples\empbuild\employee.fdb"
goto mc
After 30 minutes of execution, the console message appears:
Statement failed, SQLSTATE = HY001
unable to allocate memory from operating system
After line 0 in file _input.sql
Commits: b8bffbd fb9c2a4 ff4e296 86051b0 26faad3 057bd7a b9ea5ee
The text was updated successfully, but these errors were encountered: