Re: Memory leak in eval()'d code
| From: | David Walker | Date: | Sat, 29 Jun 2019 21:56:23 +0000 |
| Subject: | Re: Memory leak in eval()'d code | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-106117@lists.php.net to get a copy of this message | ||
On Sat, Jun 29, 2019 at 15:52 Nikita Popov <nikita.ppv@gmail.com> wrote:
> On Sat, Jun 29, 2019 at 11:25 PM Benjamin Morel <benjamin.morel@gmail.com>
> wrote:
>
> The leaked memory is an allocated but unused class
> entry. We could plug that particular leak -- but I should emphasize that
> the current behavior is incorrect and once the key collision issue is
> resolved this will create a new class for each eval.
To clarify; you’re saying that the behavior seen in the non scaled case is
kind of “wrong” in the sense that it’s exposing the big in naming of the
anon class. Once the bug is resolved, the two behaviors shown should mimic
each other, wherein the memory footprint would grow as in the example
eval() case.
—
Dave
>
>