Bug #73845 [Opn->Dup]: pg_connect()/pg_close() memory leak
| From: | ab@php.net | Date: | Wed, 08 Nov 2017 18:08:42 +0000 |
| Subject: | Bug #73845 [Opn->Dup]: pg_connect()/pg_close() memory leak | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-212520@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=73845&edit=1
ID: 73845
Updated by: ab@php.net
Reported by: miloslav dot hula at gmail dot com
Summary: pg_connect()/pg_close() memory leak
-Status: Open
+Status: Duplicate
Type: Bug
Package: PostgreSQL related
Operating System: Windows 10
PHP Version: 7.1.0
Block user comment: N
Private report: N
New Comment:
Fixed in the scope of bug #75419.
Thanks.
Previous Comments:
------------------------------------------------------------------------
[2016-12-30 17:50:26] miloslav dot hula at gmail dot com
Description:
------------
Memory remains occupied (24 bytes) after pg_connect()/pg_close() call. Calling gc_collect_cycles()
does not help.
It kills our daemon script which connects/disconnects to database.
Isolated on Windows 10 but happens on Debian with PHP 5.6.
Test script:
---------------
for ($i = 0; $i < 500; $i++) {
echo "$i: " . memory_get_usage()."\n";
pg_close(pg_connect("host=localhost dbname=test"));
}
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=73845&edit=1