Why handle count keeps increasing with active database connection?

Question

Hi,
I have an application in which windows handle count keeps increasing..I did not find any reason why this is happening? could you please help me out? below is the code:
I have also tried to close the database connection but not work.
using System;
using System.IO;
using System.Data.Common;
using System.Windows.Forms;
using System.Threading;
using System.Configuration;
using System.Data;
using System.Data.SqlClient;
namespace SampleAppWithDbConnection
    class Program
        private static SqlConnection _oCon = null;
        public static SqlConnection oCon
            get
                if (_oCon == null)
                    _oCon = new SqlConnection();
                return _oCon;
            set
                _oCon = value;
        public static int gIntervalo = 1000;
        [STAThread]
        public static void Main(string[] args)
            var gStrCon = ConfigurationManager.ConnectionStrings["Sql-ConnString-Token"].ToString();
            fConectaBase(oCon, gStrCon);
            fProcessa();
        private static void fProcessa()
            try
                do
                    Thread.Sleep(gIntervalo);
                while (true);
            catch (Exception)
        internal static bool fConectaBase(SqlConnection pCon, string pConnectionString = "")
            if (pCon.State != ConnectionState.Closed)
                pCon.Close();
            pCon.ConnectionString = (pConnectionString == "") ? pCon.ConnectionString : pConnectionString;
            pCon.Open();
            return true;

Answer 1

Hello Pramod,
>>I have an application in which windows handle count keeps increasing
If the windows handle(I assume you mean the object handles in Taks Manager bar) keeps increasing, it should means that the project keeps allocating new objects and does not close/dispose them. I notice that you are using ADO.NET API, I am wondering how you
manage these connections, do you close/dispose the connection immediately after using them? If not, please do it and it is recommended.
Please check if you call method to close/dispose connections in a finalize method, if so, this is not recommended since in a finalize method, these connections object would still keep alive and does not return to the connection pool, and for new connection
request, application might increase more connection number to meet the request.
You could make a test to call GC.Collect() to test if there is a memory leak, if it has, you could check this
article, or it could be also a handle leak, this
blog might be helpful for it.
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.