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
Crash caused by the locked fb_lock file [CORE6253] #6496
Comments
Commented by: Basil A. Sidorov (basid) Info from dumpchk and stack traces |
Modified by: Basil A. Sidorov (basid)Attachment: CORE6253.zip [ 13425 ] |
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Commented by: @hvlad The crash and its direct reason is fixed but the problem with locked attachments still remains. |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 2 [ 10888 ] Fix Version: 3.0.6 [ 10889 ] |
Commented by: Basil A. Sidorov (basid) Not resolved - crash on WI-V3.0.6.33281 Firebird 3.0. |
Modified by: @dyemanovsecurity: Developers [ 10012 ] => |
Modified by: @dyemanovsummary: Crash via locked fb_lock file => Crash caused by the locked fb_lock file |
Commented by: @hvlad Additional pathes was committed: |
Modified by: @hvladstatus: Reopened [ 4 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 RC 1 [ 10930 ] Fix Version: 3.0.7 [ 10940 ] Fix Version: 4.0 Beta 2 [ 10888 ] => Fix Version: 3.0.6 [ 10889 ] => |
Submitted by: Basil A. Sidorov (basid)
Attachments:
CORE-6253.zip
1. Run Firebird server as application or service, connect in isql to localhost:employee
2. Run fb_lock_print -d employee -iw 1 65535
3. Disconnect from employee and (normal) shutdown server. fb_lock_#### file is not deleted (open in fb_lock_print)
3. Run again Firebird server and try again connect to employee. ISQL hung and server fully load one cpu core
4. Terminate (Ctrl+C) fb_lock_print and server is crashed.
Commits: d5fad96 8348349 a1116fe f470a21 6aa0609 57599e6
The text was updated successfully, but these errors were encountered: