Hi internals,
I've tracked down a memory leak to an anonymous class created within eval():
```
for ($i = 0; $i < 100; $i++) {
$object = eval('return new class {};');
if ($i % 1000 == 0) {
echo memory_get_usage() . "\n";
}
}
```
The memory usage quick
Brief update:
We found a few more PHP DOM compatibility bugs, including one with
DOMNode::normalize(): https://bugs.php.net/bug.php?id=78221
In addition, one of our engineers implemented a pure-PHP DOM
implementation: https://github.com/linehan/DOMOperator
We're not using that in production yet,
On 26-06-19 23:22, Arnold Daniels wrote:
>
> I would argue the following; The explicit use of the strict_operator is
> intentional, meaning that the author consciously chose to be strict and
> does not expect some operators to still be non-strict. The issues pointed
> out, apply to all comparison
