Bug #38844 System.Threading.SemaphoreFullException was unhandled
Submitted: 18 Aug 2008 9:18 Modified: 25 Sep 2008 9:29
Reporter: Rohit Khare Email Updates:
Status: No Feedback Impact on me:
None 
Category:Connector / NET Severity:S2 (Serious)
Version:5.1.6 OS:Windows (XP SP2)
Assigned to: CPU Architecture:Any

[18 Aug 2008 9:18] Rohit Khare
Description:
I am developing a Windows Forms application using C# 2.0 and MySQL 5.1. When I run my project and does not perform any database operation and close project, everything works fine. But when I run a project and perform any call to database and than close my application, it generates following exception:

-----------------------------------
System.Threading.SemaphoreFullException was unhandled
  Message="Adding the given count to the semaphore would cause it to exceed its maximum count."
  Source="System"
  StackTrace:
       at System.Threading.Semaphore.Release(Int32 releaseCount)
       at System.Threading.Semaphore.Release()
       at MySql.Data.MySqlClient.MySqlPool.RemoveConnection(Driver driver)
       at MySql.Data.MySqlClient.MySqlPoolManager.RemoveConnection(Driver driver)
       at MySql.Data.MySqlClient.NativeDriver.Dispose(Boolean disposing)
       at MySql.Data.MySqlClient.Driver.Close()
       at MySql.Data.MySqlClient.NativeDriver.Finalize()
-----------------------------------

What is the meaning of this exeception and how to get rid of this?

How to repeat:
Buid any Windows Forms application in Visual Studio 2005. When you have access database few times and than close your application, this exception will occur.
[25 Aug 2008 9:29] Tonci Grgin
Hi Rohit and thanks for your report. There are many many duplicates of it, see Bug#38476 (Bug#30642, Bug#33682, Bug#36688) for example, so please do search BugsDB.

As for urgent solutions/fixes, you'll need support contract.
[25 Sep 2008 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".