[4.x] fixed frontend request polling memory leaks #1086
Merged
Conversation
This file contains 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
|
Prs without a sufficient explanation will be closed. |
|
updated description |
|
Thanks for the pr @myckhel! |
|
Its a lie!!! 😮 Thanks taylor |
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.
When component sends network request, the network response still gets processed after the initiated component has been unmounted which causes the response to initiate another
checkForNewEntriesrequest.Given the screenshot below, duplicate requests were being made after navigating from one watch section to another.
This pull request prevents watch component from processing network response after component has been unmounted.