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 on Inputs causing constant server failures (SSR) #6206

Closed
2 of 9 tasks
KhaledGabr opened this issue Dec 11, 2023 · 0 comments
Closed
2 of 9 tasks
Assignees
Labels
P1 This issue has high priority S1 This issue has high severity

Comments

@KhaledGabr
Copy link
Contributor

KhaledGabr commented Dec 11, 2023

Playground Link

https://github.com/KhaledGabr/ssr-test/tree/main

Description

The memory leak is happening on the server, often resulting in a ~1.5mb leak per page visit in my application. This creates a downtime every ~200 requests or so since all of the 500mb ram gets consumed and the server needs to be restarted.

I have created a repo where I isolated that issue and attached an image of the leak:

To reproduce:

  • Check out the branch
  • npm build
  • npm run serve:ssr (This will inspect the server using node --inspect)
  • http://localhost:4000/input
  • As you can see in the image below, I took a snapshot, refreshed the page several times, and took another snapshot.

image

Angular version

No response

Taiga UI version

3.57.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 Dec 11, 2023
@waterplea waterplea added P1 This issue has high priority S1 This issue has high severity and removed state: need triage labels Dec 11, 2023
@github-project-automation github-project-automation bot moved this from 💡 Backlog to ✅ Done in Taiga-family Dec 24, 2023
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