-
Notifications
You must be signed in to change notification settings - Fork 281
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 #1005
Comments
Hi @8HoLoN , You can post your comments here. Apart from that, could you answer the following questions?:
Thanks. |
Hi, |
Nop, nothing has reduced!! How can you say that ?! |
Got it and apologies for the confusion! Just to clarify, was the second screenshot taken right after launching the app, or did you wait some time before capturing it? We're trying to differentiate the minimum RAM usage at startup. This definitely looks like a memory leak. Based on checks of internal SDK structures and local node memory usage, the values should be lower and stable, and they shouldn't increase if no operations are performed. Could you please create a bug report directly from the app? That will allow us to contact you and request additional details. Once the team assigns your case, please share your helpdesk ID reference here. Thanks for your cooperation. |
Yes, I have waited maybe 20 min this time. The initial (normal) RAM consumption is about 60Mo The ticket ID is GVR-408-63660 @vtmateos |
The app seems to have a memory leak at least from version 5.4.1 and 5.5.0.
The process grows of 0.6 Mo each second and consume 10% of cpu in idle.
Here a screenshot with 20Go of Ram used!!
The text was updated successfully, but these errors were encountered: