Merged
Conversation
2720a30 to
9aba083
Compare
Closed
d398b10 to
7061b91
Compare
b96303d to
607bf72
Compare
Member
Author
|
I verified 1600 iterations of unit tests: the one failure is leaky experiment correctly detected. |
DarkSide666
approved these changes
Oct 7, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #1669
All tests must be able to run 1 000 000 times without any memory increase 😄
The following usecases are leaky by design:
minimal leak per iteration, leaks when the array is resized (4x, 8x, 16x, ...)
https://3v4l.org/JAMjY
leaks when php resizes class table (also in multiple of 2, but as many classes are normally already present, takes much more iterations to detect)
https://3v4l.org/jrqso (demo should include the code below in a look and the results depends if opcache is enabled)