Stumped on memory leak ODBC connection
-
I have a Console.ReadLine() at the end, did you hit return after the 99th connection?
-
This post is deleted!
-
Ok, so I commented out the open, and that's what happened was a handle leak.
When I downloaded and installed SQL LocalDB, and then uncommented the open statement, it seems to have stopped leaking handles.
With successful connections it bounces between 334 and 339 handles.
-
That's around what I was seeing. Serious :WTF:-ery
-
So, there's something that our driver for our proprietary db, is not implementing, that the sql driver is implementing, that takes the connection object out of the state where it is leaking handles.
Yeah, that's going to be easy to figure out.
I wonder how much easier it would be to implement linq queries against our API
-
It gets worse.
I let it run, it never leaked handles, when it got to the console.read... it started leaking handles.
-
Random throw shit at a wall idea: is your system language US English?Okay I'm seeing the handle count creep on the ReadLine(). That looks like a maybe .NET bug but good look convincing anyone to spend the energy on fixing that one. Now I'm gonna go off and see if Java does the same thing...
-
Can you use a wait handle?
-
Dude. We have apps being developed in Filemaker RIGHT THE FUCK NOW. Not maintenance. New. Build.
-
Dude. Ok.
... were you making some kind of point, or...?
-
Just had a "my fucking company is incompetent" seizure when I read your post and was compelled to reply. It's kind of like tourettes, but I compulsively shout out the bullshit I deal with every day.
-
I got the handle creep as long as the connection wasn't open.
If I keep it open, the handle count doesn't creep.I set mine to an infinite loop, it was not stopped at the ReadLine().