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
FesTransaction.Commit - Update event handlers NullReferenceException [DNET476] #466
Comments
Commented by: devvvy (devvvy) I suspect I fixed the issue by putting a lock around all places where this.Transaction.Update is decremented and/or set to null: lock (FirebirdSql.Data.Client.Native.FesTransaction.UpdateSyncRoot) And also in FesTransaction.Commit, public void Commit() Can anyone confirm if this is a proper fix please? Thank you very much. |
Commented by: @cincuranet Can you confirm the issue is still happening with latest version (3.x)? |
Commented by: devvvy (devvvy) sorry i don't think i will have time to upgrade for coming few months. |
Commented by: Jean-Pierre Schober (jpschober) I run into the same problem and can confirm that it still exists in release 3.0.2. |
Modified by: Jean-Pierre Schober (jpschober)Attachment: firebird_commit_nullref.patch [ 12310 ] |
Modified by: @cincuranet |
Modified by: @cincuranetstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @cincuranetstatus: In Progress [ 3 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 5.0.5.0 [ 10760 ] |
Submitted by: devvvy (devvvy)
Relate to DNET689
Attachments:
firebird_commit_nullref.patch
Votes: 1
Stack:
> FirebirdSql.Data.FirebirdClient.dll!FirebirdSql.Data.Client.Native.FesTransaction.Commit() Line 249 C#
FirebirdSql.Data.FirebirdClient.dll!FirebirdSql.Data.FirebirdClient.FbTransaction.Commit() Line 169 + 0xc bytes C#
...
I ran into a (System.NullReferenceException: Object reference not set to an instance of an object) from FesTransaction.Commit, and I have no clue what's happenning... as my code from BeginTransaction to Commit is not-threaded...
public void Commit()
{
this.CheckTransactionState();
The text was updated successfully, but these errors were encountered: