Hi Pavel, > -----Original Message----- > From: Pavel Konovalov [mailto:[EMAIL PROTECTED] > Sent: Donnerstag, 15. Juli 2004 10:49 > To: [EMAIL PROTECTED] > Subject: Descriptor and memory leak in odbc driver (from 7.3 > to 7.5 includes) > > > > > It is likely that a descriptor and memory leak in the MaxDB > ODBC driver on > Wondows 2000 . > > So, the number of descriptors and allocate memory in test > process in Windows > system monitor before performing and after that get the > increase first once > in 82 but then in 4 descriptors on every Open/Close operation.
This is a known issue. Unfortunalely I didn't find the mail where I described it. So once again: The driver manager unloads a driver, if the last environment of this driver is released. There exists some initialization code within the ODBC driver, which runs by loading the driver and which allocates some resources. Due to some internal restrictions this can not easily given back, if the driver is unloaded. The effect is visible in applications like you describe in your mail. However, this problem is not so severe as it seems. It does not happen, if you use a connection pool for your applications, since then environments and connections are reused and nothing will be unloaded. Own applications can easily overcome the problem by allocating an environment that will only be freed by leaving the application. Please apologize any inconvenience > P.S. Why change order of database and server name fields in > ODBC 7.5 data > source admin window? Please, change the TAB order too or return as be > earlier. This is already fixed and will be available in the next release. Thomas ---------------------------------------------- Dr. Thomas Kцtter SAP AG, SAP Labs Berlin Do you know SAP^H^H^H MaxDB ? www.sapdb.org -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
