Possible memory leak with ODP.Net 2.112.3.0 on Oracle 11g

887788 Feb 8, 2013 4:43 AM

Currently Being Moderated

Hi,

I am using ODP.Net 2.112.3.0 to connect my 32 bit Dot Net 2.0 windows application to Oracle 11g (Release 11.2.0.1.0 - 64 bit). The applications private working set memory kept on increasing and after few days the application crashes when private working set crosses 1 GB.
I am disposing reader, connection and command objects where ever I used, tried with 'using' also. I am using connection pooling in my application, when I don't use connection pooling I don't see much increase in private working set memory but it is badly affecting the performance.
Did any one had this problem? I will be much grateful for any insights on this problem.

Thanks
-Jason

1. Re: Possible memory leak with ODP.Net 2.112.3.0 on Oracle 11g

Tridus Feb 8, 2013 9:30 AM (in response to 887788)

Currently Being Moderated

No idea if this will help or not, but I've seen issues like this when running console applications where Main() is decorated with [STAThread]. The simplest solution is to change it to [MTAThread]. The problem is related to the garbage collector not actually getting to dispose of things properly. Some more info here: http://support.microsoft.com/kb/828988

If you're talking about a Forms application or something like that, this advise doesn't apply.
Report Abuse

Like (0)
2. Re: Possible memory leak with ODP.Net 2.112.3.0 on Oracle 11g

887788 Feb 8, 2013 5:50 PM (in response to 887788)

Currently Being Moderated

Hi Tridus,

Thanks for your reply. It is a console application and I am already using 'MTAThread' instead of 'STAThread'. Sorry, I haven't mentioned.

-Thanks
Jason
Report Abuse

Like (0)

Go to original post

Actions

Legend

Correct Answers - 10 points
Helpful Answers - 5 points