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

realtime graphs consuming too much memory #2270

Closed
majed17 opened this issue Jan 4, 2019 · 6 comments
Closed

realtime graphs consuming too much memory #2270

majed17 opened this issue Jan 4, 2019 · 6 comments
Labels
resolved A fixed issue

Comments

@majed17
Copy link

majed17 commented Jan 4, 2019

Doesn't matter what browser i use, after a few hours of graphing, all 16GB of ram get consumed and i have to end the browser task in task manager. this is on win 10 1809. I tried the 1.2 beta but with the size feature, the ram seems to be used even faster! on the 1.2.0, the problem remains with 9 graphs open, with settings: 1 hour 20 sec refresh. what is the root of the problem?

@cigamit
Copy link
Member

cigamit commented Jan 4, 2019

Are you using realtime in a popup window or inline on the graphs page? What browser and version of browser are you using for this? We've had this reported, but both Chrome and Firefox, though they did consume memory over time, they released that memory dynamically. This test was done for inline graphs and not popup. Please confirm.

@majed17
Copy link
Author

majed17 commented Jan 4, 2019

it's popup, i tried firefox, opera, ie11, and now edge...

@cigamit
Copy link
Member

cigamit commented Jan 4, 2019

This should be resolved now. In the end, I did a leak hunt, but the big culprit was some stuff going on, or that should have been going on in jQueryUI. There is an open bug. There was a published workaround. So, I used it.

@cigamit
Copy link
Member

cigamit commented Jan 4, 2019

Please test the few files that were a part of this set.

cigamit added a commit that referenced this issue Jan 4, 2019
Resolving this and a few other minor memory leaks.  Everything should
and have been validated to be working properly now.  There were a few
additional issues I found in performing a full regression.
@cigamit
Copy link
Member

cigamit commented Jan 5, 2019

Working like a champ now.

@cigamit cigamit closed this as completed Jan 5, 2019
@cigamit cigamit added the resolved A fixed issue label Jan 8, 2019
@majed17
Copy link
Author

majed17 commented Jan 11, 2019

so i tested it for a few days before i open my mouth, and indeed it is pure magic! :)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

2 participants