#35223 [Fbk]: Memory Leak (odbc_connect and odbc_close)

ID: 35223 Updated by: kalowsky@php.net Reported By: manelcaro at gmail dot com Status: Feedback Bug Type: ODBC related Operating System: Windows 2003 Server PHP Version: 5CVS, 4CVS (2005-11-15) (snap) New Comment: Woah, wait a second here Tony. Unfortunatley Windows 2003 is a real OS, so please keep the OS advocacy out of this forum. Let's stick to the bug. A better series of questions will be: What driver manager are you using? What exactly is MAXDB, and which version of ODBC is it compliant to? Have you tried altering your cursor to a different type? Previous Comments: ------------------------------------------------------------------------ [2005-11-16 00:19:42] tony2001@php.net Why did you decide it's a memory leak? How exactly did you discover it? How exactly does it crash? (if possible, please try it on a real OS where you're able to get a backtrace, not just a useless address that points to nowhere). Thanks. ------------------------------------------------------------------------ [2005-11-15 15:24:22] manelcaro at gmail dot com With this it does not happen: <?php echo "foobar"; ?> Manel. ------------------------------------------------------------------------ [2005-11-15 13:25:10] sniper@php.net Does it leak when you don't use any of those funcs? ie. with something like: <?php echo "foobar"; ?> ------------------------------------------------------------------------ [2005-11-15 11:08:08] manelcaro at gmail dot com I test php5-win32-lastest.zip and the result is the same, I test two methods: 1) with odbc_connect and odbc_close 2) with PDO $dbh = new PDO('odbc:NMSTOC', "xxxx", "xxxx"); $dbh = null; Thanks Manel ------------------------------------------------------------------------ [2005-11-15 09:31:38] sniper@php.net Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip And use the PDO ODBC. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/35223 -- Edit this bug report at http://bugs.php.net/?id=35223&edit=1