This repository has been archived by the owner on Dec 13, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 34
Fix frontend memory leaks #1071
Labels
Milestone
Comments
Yes, memory does leaking in application. Possible places (not limited to):
Major memory wasters:
Other resource-consuming sources might include Websockets, need to carefully verify what they're referring and ensure data gets freed when not needed. |
please keep in mind that this is needed, but risky change |
this story will result large impact on many areas on site. So needs to be carefully checked both on dev and QA ends. QA phase might take significant time. |
Try to switch between forms and document lists for example. |
wiadev
added a commit
that referenced
this issue
Aug 16, 2017
teosarca
added a commit
that referenced
this issue
Aug 16, 2017
Checked for memory leaks, event handlers cleanup #1071
metas-mk
added a commit
to metasfresh/metasfresh
that referenced
this issue
Aug 16, 2017
Adding new issue to release 5.23 metasfresh/metasfresh-webui-frontend-legacy#1071 Fix frontend memory leaks
IT |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to reproduce
It seems the frontend consumes quite a lot of memory (might be some memory leaks?).
My test case was:
Expected behavior
Identify the fix the memory leaks.
Thanks @wiadev for bringing this up.
The text was updated successfully, but these errors were encountered: