Random crash: NullReferenceException and invalid database handle. Crashing demo application available. [DNET727] #671
Comments
Modified by: Eric Bole-Feysot (ericbf)description: Hi System.NullReferenceException: Object reference not set to an instance of an object. invalid database handle (no active connection) I suppose both are related. It happens during the dispose of objects. Currently I'm stuck in v4.8.1 (in fact I did a v4.8.2 with a dirty hack to catch the exception and I didn't see any side effect so far), but I would like to catch up with the latest release. Thanks for your work and I hope you will find a fix as it is very annoying. Eric => Hi System.NullReferenceException: Object reference not set to an instance of an object. invalid database handle (no active connection) I suppose both are related. It happens during the dispose of objects. The crash seems more frequent on my desktop computer as on my desktop... Currently I'm stuck in v4.8.1 (in fact I did a v4.8.2 with a dirty hack to catch the exception and I didn't see any side effect so far), but I would like to catch up with the latest release. Thanks for your work and I hope you will find a fix as it is very annoying. Eric summary: Random crash: NullReferenceException and invalid database handle (crashing application available) => Random crash: NullReferenceException and invalid database handle. Crashing demo application available. |
Modified by: Eric Bole-Feysot (ericbf)description: Hi System.NullReferenceException: Object reference not set to an instance of an object. invalid database handle (no active connection) I suppose both are related. It happens during the dispose of objects. The crash seems more frequent on my desktop computer as on my desktop... Currently I'm stuck in v4.8.1 (in fact I did a v4.8.2 with a dirty hack to catch the exception and I didn't see any side effect so far), but I would like to catch up with the latest release. Thanks for your work and I hope you will find a fix as it is very annoying. Eric => Hi System.NullReferenceException: Object reference not set to an instance of an object. invalid database handle (no active connection) I suppose both are related. It happens during the dispose of objects. The crash seems more frequent on my desktop computer than on my laptop... Currently I'm stuck in v4.8.1 (in fact I did a v4.8.2 with a dirty hack to catch the exception and I didn't see any side effect so far), but I would like to catch up with the latest release. Thanks for your work and I hope you will find a fix as it is very annoying. Eric |
Modified by: @cincuranet |
Modified by: @cincuranetstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: vNext - Finalizers [ 10807 ] |
Submitted by: Eric Bole-Feysot (ericbf)
Is related to DNET698
Votes: 1
Hi
I would like to report some random crashes I met since v4.8.1 on FirebirdSql.Data.Client. It happens randomly so it is not easy to reproduce. One of my app user reported this bug some days ago and I took a new look at it.
I manage to modify my application to reproduce this bug (still random). It is a multithreaded app with firebird 2.5.6.
I tried with the latest 5.7.0 and it is still there.
System.NullReferenceException: Object reference not set to an instance of an object.
at FirebirdSql.Data.FirebirdClient.FbCommand.Release() in C:\Users\Jiri\Documents\devel\NETProvider\working\Provider\src\FirebirdSql.Data.FirebirdClient\FirebirdClient\FbCommand.cs:line 832
at FirebirdSql.Data.FirebirdClient.FbCommand.Dispose(Boolean disposing) in C:\Users\Jiri\Documents\devel\NETProvider\working\Provider\src\FirebirdSql.Data.FirebirdClient\FirebirdClient\FbCommand.cs:line 376
at System.ComponentModel.Component.Finalize()
invalid database handle (no active connection)
at FirebirdSql.Data.Client.Native.FesDatabase.ProcessStatusVector(IntPtr[] statusVector) in C:\Users\Jiri\Documents\devel\NETProvider\working\Provider\src\FirebirdSql.Data.FirebirdClient\Client\Native\FesDatabase.cs:line 365
at FirebirdSql.Data.Client.Native.FesStatement.Free(Int32 option) in C:\Users\Jiri\Documents\devel\NETProvider\working\Provider\src\FirebirdSql.Data.FirebirdClient\Client\Native\FesStatement.cs:line 621
at FirebirdSql.Data.Common.StatementBase.Release() in C:\Users\Jiri\Documents\devel\NETProvider\working\Provider\src\FirebirdSql.Data.FirebirdClient\Common\StatementBase.cs:line 241
at FirebirdSql.Data.Client.Native.FesStatement.Release() in C:\Users\Jiri\Documents\devel\NETProvider\working\Provider\src\FirebirdSql.Data.FirebirdClient\Client\Native\FesStatement.cs:line 246
at FirebirdSql.Data.Client.Native.FesStatement.Dispose(Boolean disposing) in C:\Users\Jiri\Documents\devel\NETProvider\working\Provider\src\FirebirdSql.Data.FirebirdClient\Client\Native\FesStatement.cs:line 181
at FirebirdSql.Data.FirebirdClient.FbCommand.Release() in C:\Users\Jiri\Documents\devel\NETProvider\working\Provider\src\FirebirdSql.Data.FirebirdClient\FirebirdClient\FbCommand.cs:line 838
at FirebirdSql.Data.FirebirdClient.FbCommand.Dispose(Boolean disposing) in C:\Users\Jiri\Documents\devel\NETProvider\working\Provider\src\FirebirdSql.Data.FirebirdClient\FirebirdClient\FbCommand.cs:line 376
at System.ComponentModel.Component.Finalize()
I suppose both are related. It happens during the dispose of objects.
I got a compiled application (46 MB). Tell me if you want to give it a try and I will upload it to my domain server.
The crash seems more frequent on my desktop computer than on my laptop...
Currently I'm stuck in v4.8.1 (in fact I did a v4.8.2 with a dirty hack to catch the exception and I didn't see any side effect so far), but I would like to catch up with the latest release.
Thanks for your work and I hope you will find a fix as it is very annoying.
Eric
The text was updated successfully, but these errors were encountered: