Great!

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.

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.

And most people who work on PHP do this actually as a hobby and do not get paid.

So the minimum is to be polite.

@girgias@php.net I couldnt care less for people that fork PHP and do it as a hobby. What I do as my hobby is not your business, and what you do on your spare time, is not my business. I will not be glad to you that your hobby is A, B or C. As I dont expect at all that you will be glad if my hobby is forking PHP and solving bugs. 

I dont know if you have any idea of what is a hobby, but generally a hobby is something where you put your time, effort, money... into and expect nothing but happines, inner peace... If you expect money from a hobby, it's a job. If you expect people praising your name, thanking you for your hobby, it's not a job, it's selfishness and peacockery.

gilperon at gmail dot com: you don't get it!

most of the developers are not paid, that's it, no tmore and not less
compared to other programming languages PHP has envolvd a lot in the past few years *without* breaking changes, period

rtrtrtrtrt at dfdfdfdf dot dfd OF COURSE I know people are not being paid here. Of course I know that. But if you have spare time to maintain PHP source code as your hobby, you shouldnt expect people to pray for you. I also dont exepct people to pray for me when I waste my time coming here, reporting a bug, creating a test case... nobody comes to me and say "thank you, you are a great person for reporting this bug, take here $ 1 for your time". Both sides are doing their best to the project, wheter reporting of fixing bugs.