Re: Ifxoledbc memory leak

Posted in 2003

Tsutomu Ogiwara — Mon, 14 Jul 2003 12:00:56 +0900 — source: Usenet: comp.databases.informix

Hi Mladen. I have silimilar experience with ODBC 3.34. Is is a bug as bellow. 156698 USING GLS WITH ODBC COUPLE OF BIG MEMORY LEAKS.SEE LONG DESCRIPTION. This problem is solved in ODBC 3.82. It is buldled I-CONNECT and I-CSDK 2.81.TC2. Try latest vertion. Hope this helps. -- Tsutomu Ogiwara from Tokyo Japan. ICQ#:168106592 >From: "Mladen Turk" <mturk@apache.org> >Reply-To: "Mladen Turk" <mturk@apache.org> >To: informix-list@iiug.org >Subject: Ifxoledbc memory leak >Date: Sat, 12 Jul 2003 17:18:29 +0200 > >Hi, > >Something that cost me 5 days to trace... > >Using ADO and the latest CSDK (2.81 + 9.4 on the server side all are >WIN2KSP3 ) I found that the the: > >IRecordset->Open(...) >.. >IRecordset->Close() > >causes 68 bytes memory leak. >Well, after 100000 calls to to db, the entire thing chrashes. > >Of course, I drilled down to my code, but... > >The same code works perfectly if I change the connection string from >"Povider=Ifxoledbc.2" to "Provider=MSDASQL.1" > >So, using MS OLEDB for ODBC provider instead Ifxoledbc resolved the memory >crush, but the drawbacks are fascinating. > >1. When using Ifxoledbc the client is on 70% CPU and the Server is on 42% >CPU. Each Open/Close recordset consumes 68 bytes of memory. >2. When using MS OLEDB for ODBC there are no memory leak at all, but the >client is on 12% and the server is on 98%, and the performance is 20 times >slower. > >Do you guys need some C programmer? >I'll do it for free. > > _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 sending to informix-list