Get rid of unmounted component update in ResultList#26143
Merged
Conversation
ryanclark
approved these changes
May 12, 2023
|
@ravicious See the table below for backport results.
|
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.
Reproduction steps:
Strangely enough, this happen only the first time you do this, not on subsequent calls.
ResultListis rendered byActionPickerandParameterPicker.onPickon an SSH server or a database callschangeActivePickerfromSearchContextwhich unmountsActionPickerand mountsParameterPicker.Still, this doesn't explain how the leak happens. I was under the impression that React first processes all state updates and only then re-renders the components.
Well, that's true, but only for React 18. React 17 does not batch the state updates in certain cases, for example when executing native event listeners.
It just so happens that
pickAndResetActiveItemis called from an event listener that is added directly onwindowwithaddEventListener.By calling
setActiveItemIndexfirst we make sure that this state update is processed beforeonPickpotentially causesResultListto unmount.