|
[
Permalink
| « Hide
]
Basil A. Sidorov added a comment - 20/Feb/20 01:05 PM
Info from dumpchk and stack traces
Not resolved - crash on WI-V3.0.6.33281 Firebird 3.0.
Additional pathes was committed:
- fb_lock_print in interactive mode checks every second if lock table is empty and breaks iterations to release shared memory and avoid of blocking new attachments, - shared memory initialization code now tries to handle case when last process that holds shared memory was killed (or crashed) and OS objects (event, memory mapping, etc) was released in not correct\expected order. It pevents bugcheck in lock manager in such a case. |