|Subject||Re: FB2.5 crash|
> First the demo application for fb2.1.4 will be available this afternoon...If it is ready i'll be glad to try it.
> > What build do you use ? The preferable is to use most current snapshot build, as it contains many fixes since RC2.At the same site, see http://www.firebirdsql.org/download/snapshot_builds/
> Hm, i use the build on firebirdsql.org (RC2)
> where i can download the current snapshot?
> some time ago someone say me that the rc3 will be available very soon (in one or 2 weeks).. is it still so ?We still make some additional tests on it.
> YES, their is all this file :Very good. Can i look at fb_lock_table.dump (and firebird.log too) ?
> 04/11/2010 08:50 AM 65,536 fb_event_0ae46cbc000003002a000000
> 04/11/2010 08:50 AM 1,048,576 fb_lock_0ae46cbc000001002b000000
> 04/12/2010 02:27 AM 6,291,456 fb_lock_0ae46cbc000003002a000000
> 04/11/2010 08:50 AM 1,048,576 fb_lock_97bae51a0000020098e70000
> 04/11/2010 08:50 AM 5,640,728 fb_lock_table.dump
> 04/11/2010 09:47 AM 1,048,576 fb_monitor_0ae46cbc000003002a000000
> 04/11/2010 08:50 AM 276 fb_trace
> 04/10/2010 09:05 AM 0 fb_trace_m67kh4
> 04/11/2010 08:50 AM 0 fb_trace_mjmhw5
> 04/12/2010 10:19 AM 0 s
> it's can help you ?
Also, i see you used events ? Just for info :)
> > It is suspicious that this error happens at the same moment as "invalid lock id".There could be race condition in INET code at process shutdown. I.e. WSACleanup() was called before all existing connections disconnected.
> yea ;) but the question is what cause the other
> invalid lock id cause the WSANOTINITIALISED
> or the WSANOTINITIALISED cause the invalid lock id ?
Process shutdown happens because of "invalid lock id" error.
It (INET errors) seems for me as minor issue as it doesn't prevent process shutdown and hurts nothing. Anyway i'll investigate it.