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

[Bug]: Memory Leak and Performance Issues #68

Open
1 task done
Swapnilden opened this issue Jun 26, 2024 · 1 comment
Open
1 task done

[Bug]: Memory Leak and Performance Issues #68

Swapnilden opened this issue Jun 26, 2024 · 1 comment
Labels

Comments

@Swapnilden
Copy link

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 📄

  1. Observe Performance: Move the mouse rapidly across the screen and observe the performance. Note any lag or increased memory usage.
  2. Check Element Creation: Monitor the number of DOM elements created during mouse movement. Use browser developer tools to inspect the DOM.
  3. Implement Throttling: Introduce a throttle function to limit the number of ripples created.
  4. Validate Improvement: Test the application again to ensure improved performance and reduced memory usage.

Select program in which you are contributing

GSSoC24

Code of Conduct

@github-actions github-actions bot added the gssoc label Jun 26, 2024
Copy link

Hey @Swapnilden! 👋

👉 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 Swapnilden changed the title [Bug]: [Bug]: Memory Leak and Performance Issues Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant