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.

Sign up for GitHub

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

Jump to bottom

Memory leak #154

Open
nadezhday opened this issue Jan 22, 2020 · 1 comment
Open

Memory leak #154

nadezhday opened this issue Jan 22, 2020 · 1 comment
Labels
backend bug is related to backend bug something doesn't work as expected. Has sub-labels: regression, backend, frontend, critical critical bug is critical for the whole system. Should be fixed in the first place frontend bug is related to frontend

Comments

@nadezhday
Copy link

During testing sometimes we get in situation when Memory usage started to grow (possible memory leak).
There are no exact steps to reproduce.
Here is a screenshot:
image
Can we do anything about it?
@nadezhday nadezhday added the bug something doesn't work as expected. Has sub-labels: regression, backend, frontend, critical label Jan 22, 2020
@al-indigo al-indigo added backend bug is related to backend frontend bug is related to frontend labels Jan 29, 2020
@al-indigo
Copy link
Member

Known issue, needs redesign both backend and frontend for websockets (for graphql and subscriptions for events). Not assigning yet

@nadezhday nadezhday added the critical bug is critical for the whole system. Should be fixed in the first place label Sep 23, 2020
@myrix myrix mentioned this issue Apr 4, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backend bug is related to backend bug something doesn't work as expected. Has sub-labels: regression, backend, frontend, critical critical bug is critical for the whole system. Should be fixed in the first place frontend bug is related to frontend
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@al-indigo @nadezhday