Fix NullReferenceException when disposing transactions (race conditon (?)) #573
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running in a relatively heavy load scenario, Npgsql will occasionally (very rarely) fail when disposing transactions that aborted prematurely. I am unable to reproduce the issue consistently, but have a patch which (I think) fixes the problem.
When this exception occurs the logged stack trace I am seeing is this:
This pull request guards against
NpgsqlConnectorreferences beingnull. I cannot be certain that the connector reference is the culprit, but since running with the patch in place I have not observed any moreNullReferenceExceptions.