[
http://tracker.firebirdsql.org/browse/CORE-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Khorsun reopened CORE-6253:
--------------------------------
> Crash caused by the locked fb_lock file
> ---------------------------------------
>
> Key: CORE-6253
> URL: http://tracker.firebirdsql.org/browse/CORE-6253
> Project: Firebird Core
> Issue Type: Bug
> Components: Engine
> Affects Versions: 4.0 Beta 1, 3.0.5
> Environment: WI-V3.0.5.33220 Firebird 3.0
> WI-T4.0.0.1779 Firebird 4.0 Beta 1
> Reporter: Basil A. Sidorov
> Assignee: Vlad Khorsun
> Priority: Minor
> Fix For: 3.0.6, 4.0 Beta 2
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
