mirror of
https://github.com/php/php-src.git
synced 2024-09-21 18:07:23 +00:00
b58d74547f
Since PHP 7.4 objects that have a destructor require two GC runs to be collected. Currently the collection is delayed to the next automatic GC run. However, in some cases this may result in a large increase in memory usage, as in one of the cases of bug #79519. See also bug #78933 and bug #81117 where the current behavior is unexpected for users. This patch will automatically rerun GC if destructors were encountered. I think this should not have much cost, because it is very likely that objects on which the destructor has been called really are garbage, so the extra GC run should not be doing wasted work. Closes GH-5581.
28 lines
350 B
PHP
28 lines
350 B
PHP
--TEST--
|
|
GC 011: GC and destructors
|
|
--INI--
|
|
zend.enable_gc=1
|
|
--FILE--
|
|
<?php
|
|
class Foo {
|
|
public $a;
|
|
function __destruct() {
|
|
echo __FUNCTION__,"\n";
|
|
}
|
|
}
|
|
$a = new Foo();
|
|
$a->a = $a;
|
|
var_dump($a);
|
|
unset($a);
|
|
var_dump(gc_collect_cycles());
|
|
echo "ok\n"
|
|
?>
|
|
--EXPECTF--
|
|
object(Foo)#%d (1) {
|
|
["a"]=>
|
|
*RECURSION*
|
|
}
|
|
__destruct
|
|
int(1)
|
|
ok
|