Bug #65689 [Asn->Csd]: PDO_Firebird memory leaks when using exec()

From: Date: Mon, 26 Dec 2016 11:04:02 +0000
Subject: Bug #65689 [Asn->Csd]: PDO_Firebird memory leaks when using exec()
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-206209@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=65689&edit=1 ID: 65689 Updated by: nikic@php.net Reported by: slavb18 at gmail dot com Summary: PDO_Firebird memory leaks when using exec() -Status: Assigned +Status: Closed Type: Bug Package: PDO Firebird Operating System: any PHP Version: 5.4.19 Assigned To: mariuz Block user comment: N Private report: N New Comment: Resolved by PR https://github.com/php/php-src/pull/2253. Previous Comments: ------------------------------------------------------------------------ [2013-10-15 17:09:19] nikic@php.net @slavb: That was an automated status change. I reverted it back to Open :) ------------------------------------------------------------------------ [2013-10-15 12:03:29] slavb18 at gmail dot com don't know why it is marked as "no feedback", but I actaully answered and supplied a patch ------------------------------------------------------------------------ [2013-10-15 11:54:51] php-bugs at lists dot php dot net No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Re-Opened". Thank you. ------------------------------------------------------------------------ [2013-09-18 05:22:08] slavb18 at gmail dot com memory leaks at firebird side, noticeable with persistent connects (process size grows constantly) I added isc_dsql_free_statement (see patch), and now is ok ------------------------------------------------------------------------ [2013-09-17 21:46:44] felipe@php.net Can you include a valgrind log of memory leak for futher analysis? ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=65689 -- Edit this bug report at https://bugs.php.net/bug.php?id=65689&edit=1

« previous php.bugs (#206209) next »