You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code in mouseEffect.js creates a new ripple element on every mouse movement, leading to potential memory leaks and performance degradation.
What is the expected behavior? 🤔
The ripple effect should only be triggered under specific conditions, such as throttled mouse movements or click events, to avoid performance issues and memory leaks.
Provide step by step information reproduce the bug 📄
Observe Performance: Move the mouse rapidly across the screen and observe the performance. Note any lag or increased memory usage.
Check Element Creation: Monitor the number of DOM elements created during mouse movement. Use browser developer tools to inspect the DOM.
Implement Throttling: Introduce a throttle function to limit the number of ripples created.
Validate Improvement: Test the application again to ensure improved performance and reduced memory usage.
👉 Thanks for opening this issue. We appreciate your contribution and will look into it as soon as possible.
👉 Don’t forget to star our Formation-Absent and Follow Us on GitHub
👉 Make sure you join our Discord, we have created separate channels for all projects
Swapnilden
changed the title
[Bug]:
[Bug]: Memory Leak and Performance Issues
Jun 26, 2024
Give a brief about the bug ✍️
The code in mouseEffect.js creates a new ripple element on every mouse movement, leading to potential memory leaks and performance degradation.
What is the expected behavior? 🤔
The ripple effect should only be triggered under specific conditions, such as throttled mouse movements or click events, to avoid performance issues and memory leaks.
Provide step by step information reproduce the bug 📄
Select program in which you are contributing
GSSoC24
Code of Conduct
The text was updated successfully, but these errors were encountered: