sji

strrev('php-profiler') === 'reliforp-php' So "Reliforp" and "Reli (for ph*)" are the current candidates.

To test a development version of [our memory profiler](https://github.com/reliforp/reli-prof), I've tried to investigate the leak in the original issue. # Test script ```php

@lighthuter Hi! In that code you first dereferences sapi_request_info.query_string as a pointer to another pointer, and then dereferences the retrieved pointer as a pointer to Char. But actually sapi_request_info.query_string is...

@lighthuter Hi! Oh, I have overlooked a number of things. You were right about trying to get the pointer value as a 64-bit value first. Currently maybe you use the...

@lighthuter Hi! Sorry for the delay. I was busy to death. You can read the super globals via `EG(symbol_table)`. So first getting EG like [this](https://github.com/reliforp/reli-prof/blob/21aa53ed68366240663513798167995d3f4787f3/src/Lib/PhpProcessReader/CallTraceReader/CallTraceReader.php#L121) and then reading the global...

@lighthuter Oh, my bad. > `$eg->symbol_table->findByKey($dereferencer, '_SERVER')?->val->value->arr;` This code pulls a Bucket from the hash table, but as it is only used as a temporary object, the Bucket object is...

@lighthuter Hi! If you use Reli without stopping the target process via `-S` option, it's a normal behavior. The state of the target process continues to change while Reli is...

@lighthuter Hmm, then there should not be so much. Is it possible to give me simple reproduction steps? If so, please [open another issue as a bug report](https://github.com/reliforp/reli-prof/issues/new?assignees=&labels=bug&projects=&template=bug_report.md&title=%5BBUG%5D+).

@maxgalbu Hi! From the output, the total size of the top 20 memory consuming types of locations is 2,251,252 bytes at the time of the analysis. First, consider whether this...

Thanks for taking your time! I will take a closer look later.