Devart Forums

I am using the CoreLab.Postgres.dll on a couple of my web sites. About every 24 to 36 hours the dll will fail and normally reports a "System Out Of Memory" exception. Restarting the web app fixes the problem so it is assumed that this is a memory leak in the CoreLab.Postgres.dll.

Up until 3 or 4 weeks ago I'd been using Npgsql and would never have this happened. I am not doing anything fancy in my SQL just basic operations and some realtively small table joins, biggest table probably 30,000 rows.

Aaron

Is this bug present in the last version? Do you use ConnectionPool?

I'm not sure if it's version 2.10.4, I'll keep an eye out. THe bug is in 2.10.3.

I don't set any connection pooling settings manually. Is this something we need to do with PostgreSQLDirect.Net?

Other data providers I've used implement all this under the hood and you only need to modify connection pool settings if you need something different...

We couldn't reproduce the problem.
Is it server side memory leak? Please show an example of using data provider which leads to memory leak.