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
Crash of .NET application [DNET368] #373
Comments
Commented by: @cincuranet Provide steps to reproduce. |
Commented by: Radu Simen (radu103) The idea is simple: For every keystroke one command is launched and if another is pressed while the request is working, the first one is stoped. Anyway those block of code should be in a try/catch block so the application should not crash |
Commented by: Radu Simen (radu103) Maybe this will help. When this crash occured there was nothing out of the ordinary in the application. |
Modified by: Radu Simen (radu103)Attachment: fb_command_bug.png [ 11911 ] |
Commented by: Radu Simen (radu103) I think the problem is in RollbackImplicitTransaction function FbCommand.cs at line 788 int transactionCount = this.Connection.InnerConnection.Database.TransactionCount; Maybe the 'this.Connection.InnerConnection.Database.TransactionCount;' has some null values when the parent window is closed and are more transactions not disposed yet. I think a try catch there with logging to event log will be good. |
Modified by: @cincuranetstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @cincuranet |
Submitted by: Radu Simen (radu103)
Duplicates DNET316
Attachments:
fb_command_bug.png
Votes: 3
Application: App.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
Stack:
at FirebirdSql.Data.FirebirdClient.FbCommand.RollbackImplicitTransaction()
at FirebirdSql.Data.FirebirdClient.FbCommand.Release()
at FirebirdSql.Data.FirebirdClient.FbCommand.Dispose(Boolean)
at System.ComponentModel.Component.Finalize()
Taken from the Event Viewer.
The application is crashing.
Pls correct the problem
The text was updated successfully, but these errors were encountered: