-
-
Notifications
You must be signed in to change notification settings - Fork 238
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: prevent potential memory leak by properly removing watcher references #1307
Conversation
|
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.
There seems to be some unwanted formating changes which can further cause format workflow failure, can you pls. remove them by running the script npm run lint:fix
@DhairyaMajmudar I have removed the extra formatting changes. |
was this an issue coming from sonarcloud? of yes, please indicate it in description and provide to sonar report |
Quality Gate passedIssues Measures |
No, it is just an observational fix. |
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.
ok, then I will close this issue, watcher is used in CLI only and we will deprecate it in few days and it doesn't make sense to invest in any changes to it
Description
This PR addresses a potential memory leak issue in the Watcher class. When a watcher is closed, the reference to the watcher was previously set to null but not removed from the this.watchers object. Over time, this could lead to unnecessary memory consumption/memory leak.