|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #81027 WeakReference will cause memory leaks
Submitted: 2021-05-10 14:04 UTC Modified: 2021-05-13 11:11 UTC
Avg. Score:3.0 ± 0.0
Reproduced:0 of 0 (0.0%)
From: gy dot dlcs at gmail dot com Assigned:
Status: Open Package: Unknown/Other Function
PHP Version: 8.0.6 OS: Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: gy dot dlcs at gmail dot com
New email:
PHP Version: OS:


 [2021-05-10 14:04 UTC] gy dot dlcs at gmail dot com
Just like the test script, When you Uncomment the `!$wr->get();` line, You will see the memory leaks in a few seconds.

Test script:
ini_set('memory_limit', '16M');

while (true) {
    $a = new stdClass();
    $a->a = $a;

    $wr = WeakReference::create($a);

    // Uncomment next line, memory will not leak
    // $wr->get();

    // Uncomment next line, memory will leak
    // !$wr->get();

Expected result:
PHP Fatal error:  Allowed memory size of 16777216 bytes exhausted (tried to allocate 20480 bytes) in test.php on line 9


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2021-05-10 14:09 UTC] gy dot dlcs at gmail dot com
php 7.4 and 8.0 will be affected
 [2021-05-10 14:58 UTC]
-Status: Open +Status: Not a bug -Assigned To: +Assigned To: cmb
 [2021-05-10 14:58 UTC]
Sorry, but your problem does not imply a bug in PHP itself.  For a
list of more appropriate places to ask for help using PHP, please
visit as this bug system is not the
appropriate forum for asking support questions.  Due to the volume
of reports we can not explain in detail here why your report is not
a bug.  The support channels will be able to provide an explanation
for you.

Thank you for your interest in PHP.
 [2021-05-10 15:15 UTC]
I can't reproduce this.
 [2021-05-10 15:31 UTC] gy dot dlcs at gmail dot com
emmm, I reproduced it with a clean container, this is the video:
 [2021-05-10 15:43 UTC]
-Status: Not a bug +Status: Feedback
 [2021-05-10 15:43 UTC]
For me there is no difference whether ther is `$wr->get()`,
`!$wr->get()`, or neither; memory consumption increases until GC
kicks in.

Are there any leaks reported when you're running under valgrind
 [2021-05-10 16:56 UTC] gy dot dlcs at gmail dot com
I create a clean VM on Digitalocean, and reproduced it, this is the video and valgrind test result:
 [2021-05-11 06:28 UTC]
I can't reproduce this either.

In addition, I see no possible path to a leak.
 [2021-05-11 09:26 UTC]
-Assigned To: cmb +Assigned To:
 [2021-05-11 09:26 UTC]
Thanks for the valgrind report, but unfortunately this is useless.
The warnings at the top are bogus, and everything after the SIGINT
is irrelevant.  Sorry for requesting it!

I wouldn't know how to proceed with this issue.
 [2021-05-13 11:11 UTC] gy dot dlcs at gmail dot com
The above test script takes about 1 minute to reproduce the problem, Have you waited long enough?
 [2021-05-14 12:08 UTC]
I can't reproduce it with 8.0.3 but I can reproduce it with the current snapshot from GIT
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Tue Aug 03 18:01:24 2021 UTC