Fix deadlock in mysql poolmanager #60
Closed
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.
There is deadlock bug in MySqlPoolManager.cs. It makes the library unusable in any .Net applications with SynchronizationCotnext while using pooling feature.
It causes a deadlock of threads, application will hang forever. Affected are:
If using Pooling=true in connection string (common scenario).
What is more, it leads to breaking the whole appPool on IIS (for ASP .NET MVC app) as all threads from thread pool will eventually deadlock.
This looks like obvious human error, there is missing ConfigureAwait(false) when awaiting on semaphore. Note that the ConfigureAwait(false) is widely used in all other places at this class but in this one is simply missing.
In this PR:
How bug was introduced