Skip to content
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

Memory leak due to event listener #1142

Closed
4 tasks done
Palakkgoyal opened this issue Aug 5, 2023 · 3 comments · Fixed by #1180
Closed
4 tasks done

Memory leak due to event listener #1142

Palakkgoyal opened this issue Aug 5, 2023 · 3 comments · Fixed by #1180
Labels

Comments

@Palakkgoyal
Copy link
Contributor

Palakkgoyal commented Aug 5, 2023

Description

There is a event listener in the App.jsx file that is running and not getting cleared. It could cause memory leaking.

Steps to reproduce

  • Use the website for some time
  • In the DevTools => elements => event listeners => scroll
  • You will see there are so many scroll event listeners are triggered.

Screenshots

Screenshot 2023-08-04 223722

No response

Desktop (please complete the following information)

No response

Smartphone (please complete the following information)

No response

Additional information

No response

Record

  • I agree to follow this project's Code of Conduct
  • I have checked the existing issues
  • I'm a GSSoC'23 contributor
  • I want to work on this issue
@Palakkgoyal Palakkgoyal added the bug label Aug 5, 2023
@github-actions
Copy link

github-actions bot commented Aug 5, 2023

Hello Palakkgoyal!
Thank you for raising this issue! 😊 Your contribution is valuable to us! 😊

Please make sure to follow our Contributing Guidelines. 💪🏻

Our reviewers shall carefully assess the issue and reach out to you soon! 😇
We appreciate your patience!

@narayan954
Copy link
Owner

Thanks for fixing/finding!

@Palakkgoyal
Copy link
Contributor Author

No worries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants