I have an application which makes very heavy use of the MySQLDirect.NET connector v3.50.
I appear to have a memory leak where the application eventually uses up all the nonpaged memory in the system (I can see this in Task Manager).
I'm trying to narrow down where the problem may be occur - I don't use non-paged memory in my code, to my knowledge, and I am wondering whether it may be connected to MySQLDirect, or the TCP/IP stack which I'm using to access MySQL.
I'm running 5.0 on Windows XP. Any thoughts would be appreciated.
Stevod