-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dashboard] fix Memory leak when reset causes by-value panel to be deleted #161394
Conversation
…-ref HEAD~1..HEAD --fix'
💚 Build Succeeded
Metrics [docs]Page load bundle
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
To update your PR or re-run it, just comment with: |
Pinging @elastic/kibana-presentation (Team:Presentation) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! though this may conflict with #159837 because the embeddable panel file has been totally re-structured in that PR. (and has the early return!)
That said, it's worth it to merge this, because I won't be backporting that PR!
…leted (elastic#161394) Closes elastic#161310 Issue caused by `setState` call after async action without checking that component is still mounted. Resolved issue by checking component is mounted after any async action or subscription. --------- Co-authored-by: kibanamachine <[email protected]> (cherry picked from commit d9c0c55)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
… be deleted (#161394) (#161467) # Backport This will backport the following commits from `main` to `8.9`: - [[dashboard] fix Memory leak when reset causes by-value panel to be deleted (#161394)](#161394) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-07-07T14:53:50Z","message":"[dashboard] fix Memory leak when reset causes by-value panel to be deleted (#161394)\n\nCloses https://github.com/elastic/kibana/issues/161310\r\n\r\nIssue caused by `setState` call after async action without checking that\r\ncomponent is still mounted. Resolved issue by checking component is\r\nmounted after any async action or subscription.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"d9c0c554f8e54068c5fd8d0c27094f0d04c6dac3","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Embedding","Team:Presentation","release_note:skip","v8.9.0","v8.10.0","Feature:Embeddables"],"number":161394,"url":"https://github.com/elastic/kibana/pull/161394","mergeCommit":{"message":"[dashboard] fix Memory leak when reset causes by-value panel to be deleted (#161394)\n\nCloses https://github.com/elastic/kibana/issues/161310\r\n\r\nIssue caused by `setState` call after async action without checking that\r\ncomponent is still mounted. Resolved issue by checking component is\r\nmounted after any async action or subscription.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"d9c0c554f8e54068c5fd8d0c27094f0d04c6dac3"}},"sourceBranch":"main","suggestedTargetBranches":["8.9"],"targetPullRequestStates":[{"branch":"8.9","label":"v8.9.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/161394","number":161394,"mergeCommit":{"message":"[dashboard] fix Memory leak when reset causes by-value panel to be deleted (#161394)\n\nCloses https://github.com/elastic/kibana/issues/161310\r\n\r\nIssue caused by `setState` call after async action without checking that\r\ncomponent is still mounted. Resolved issue by checking component is\r\nmounted after any async action or subscription.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"d9c0c554f8e54068c5fd8d0c27094f0d04c6dac3"}}]}] BACKPORT--> Co-authored-by: Nathan Reese <[email protected]>
Closes #161310
Issue caused by
setState
call after async action without checking that component is still mounted. Resolved issue by checking component is mounted after any async action or subscription.