-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
fix component destroy leak #6522
fix component destroy leak #6522
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## development #6522 +/- ##
===============================================
- Coverage 76.98% 76.97% -0.01%
===============================================
Files 315 315
Lines 10701 10701
Branches 2988 2988
===============================================
- Hits 8238 8237 -1
- Misses 2461 2462 +1
Partials 2 2
Continue to review full report at Codecov.
|
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.
Testing completed. Locally work correctly. No critical issues were found.
Are these failures caused by my changes or it's just something random? I checked one of the tests and it looks like it's just stuck in the middle. |
failures in full e2e tests don't connect with your changes, not all tests are fixed, for some reasons |
@@ -228,6 +228,7 @@ export class ComponentLoader<T extends object> { | |||
this._contentRef?.viewRef?.destroy(); | |||
|
|||
this._contentRef = void 0; | |||
this._componentRef.destroy(); |
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.
I would go with this._componentRef?.destroy()
Was merged another PR with the same code |
fixes #6499 #5999