Bug #80200 [Nab]: On reply to nikic on https://bugs.php.net/bug.php?id=80199
Edit report at https://bugs.php.net/bug.php?id=80200&edit=1
ID: 80200
User updated by: gilperon at gmail dot com
Reported by: gilperon at gmail dot com
Summary: On reply to nikic on
https://bugs.php.net/bug.php?id=80199
Status: Not a bug
Type: Bug
Package: *General Issues
Operating System: all
PHP Version: 7.4.11
Block user comment: N
Private report: N
New Comment:
nikic@php.net I am sorry for my behaviour but I was pissed of because most of the times I report
something here, I really waste my time. And I work for living, not for hobby. When I come here to
report a bug, I am donating some of my time trying to help the community - I will not get anything
from the bug being fixed or not because I always need a solution immediatly, so I always end up
having to find a workaround the bug.
Just as a side not: I reported this bug on SO at https://stackoverflow.com/questions/64249929/why-using-eval-will-not-release-memory-later-when-using-unset-on-anonymous-f
and a guy name NIGEL REN gave me a nice solution! Instead of evaluating the function code I should
put it inside a file and require the file.
Amazingly enough, he, me and other guy on that thread realized that PHP does not clear it's
memory footprint on files included/required! That's a pretty big problem, I abuse" the
use of require in lots of my projects and I never knew that using require/include would
not clear RAM! That's pretty terrible and explains a lot why most of the cloud servers I manage
use so much RAM because I use a TON require to keep our codebase organized.
Previous Comments:
------------------------------------------------------------------------
[2020-10-07 18:38:01] nikic@php.net
Marking your report as a duplicate does not mean that it will not be addressed, only that there is
an existing report tracking this issue already. Having multiple open bugs for the same root cause is
counter-productive, as information gets spread out.
Unfortunately the issue in question is simply not easy to fix. My last attempt at it was https://github.com/php/php-src/pull/5595, which
would address your particular case of eval'd closures, but does not fully generalize to the
case of anonymous classes.
------------------------------------------------------------------------
[2020-10-07 18:35:09] great at gmail dot com
Great!
------------------------------------------------------------------------
[2020-10-07 18:31:21] gilperon at gmail dot com
Description:
------------
[2020-10-07 18:25 UTC] nikic@php.net
This is such a well known open problem that I really don't need to run your code to identify it
:)
Great nikic! Let's get this well known open problem more visibility by not getting it fixed!
That's why for most time recently I am using Golang, MUCH better implementation and community
support.
I think you believe I will get any money by coming here reporting a bug. No, I dont get anything, I
just waste my time, as all the previous attempts I made. kkk Keep doing it like this, even Microsoft
wont support PHP binaeries from 8.x and later.
Test script:
---------------
stuck your finger on your ars
Expected result:
----------------
shit should come out
Actual result:
--------------
a fart
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=80200&edit=1
Thread (8 messages)