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 with tui-input & tui-select components #6505

Closed
2 of 9 tasks
zip-fa opened this issue Jan 21, 2024 · 0 comments
Closed
2 of 9 tasks

🐞 - Memory leak with tui-input & tui-select components #6505

zip-fa opened this issue Jan 21, 2024 · 0 comments
Assignees
Labels
P1 This issue has high priority S1 This issue has high severity

Comments

@zip-fa
Copy link

zip-fa commented Jan 21, 2024

Playground Link

https://github.com/zip-fa/taiga-memory-leak

Description

Hi.
I recently noticed that the input component leaks somehow: the amount of used memory & dom nodes count are constantly increasing when cycling between the same routes.
To reproduce this, please jump between route 1 and route 2 multiple times (10x+) and call GC collector from web inspector.

Stats on initial page load:

image

Stats after 10-15 cycles:

telegram-cloud-photo-size-2-5289512277160090150-x

Observations:

  • tui-hosted-dropdown leaks
  • tui-input leaks
  • tui-select with tui-data-list-wrapper & tuiDataList inside leaks

Angular version

17.1.0

Taiga UI version

3.62.0

Which browsers have you used?

  • Chrome
  • Firefox
  • Safari
  • Edge

Which operating systems have you used?

  • macOS
  • Windows
  • Linux
  • iOS
  • Android
@github-project-automation github-project-automation bot moved this to 💡 Backlog in Taiga-family Jan 21, 2024
@waterplea waterplea added P1 This issue has high priority S1 This issue has high severity and removed state: need triage labels Jan 26, 2024
@github-project-automation github-project-automation bot moved this from 💡 Backlog to ✅ Done in Taiga-family Feb 9, 2024
@splincode splincode reopened this Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 This issue has high priority S1 This issue has high severity
Development

No branches or pull requests

4 participants