Improve memory consumption by cleaning up garbage references#35
Merged
clue merged 1 commit intoclue:masterfrom Jun 13, 2018
Merged
Improve memory consumption by cleaning up garbage references#35clue merged 1 commit intoclue:masterfrom
clue merged 1 commit intoclue:masterfrom
Conversation
Owner
Author
|
I've updated this to include a test for reactphp/promise-timer#34 which is yet to be released as part of react/promise-timer v1.5.0. |
Owner
Author
|
Updated and removed WIP marker now that https://github.com/reactphp/promise/releases/tag/v2.7.0 and https://github.com/reactphp/promise-timer/releases/tag/v1.5.0 have been released, this is now ready |
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
1 participant
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.
While debugging some very odd memory issues in a live application, I noticed that this component shows some unexpected memory consumption and memory would not immediately be freed as expected. Let's not call this a "memory leak", because memory was eventually freed, but this clearly caused some unexpected and significant memory growth.
This builds on top of the work done in reactphp/promise#113, reactphp/promise#115, reactphp/promise#116 and reactphp/promise#117 and reactphp/promise-timer#33.
I'm marking this PR as WIP because this includes a test for reactphp/promise#124 which is yet to be released as part of react/promise v2.7.0. Once this release is out, I'll update the version reference and this should be ready to be shipped.