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 #1005

Open
8HoLoN opened this issue Oct 9, 2024 · 11 comments
Open

Memory leak #1005

8HoLoN opened this issue Oct 9, 2024 · 11 comments

Comments

@8HoLoN
Copy link

8HoLoN commented Oct 9, 2024

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!!
image

@vtmateos
Copy link
Member

Hi @8HoLoN ,
Could you test with latest 5.6.1 version from our website and confirm if still happens?

You can post your comments here.

Apart from that, could you answer the following questions?:

  • Do you have any sync or backup in place?
  • Could you provide a rough estimate about the number of cloud items?
  • Could you describe the steps you made until you get to that point? A simple login with credentials, login with existing session, setting syncs and/or backup...,

Thanks.

@8HoLoN
Copy link
Author

8HoLoN commented Nov 22, 2024

I have installed the 5.6.1 version. The problem is still here.

  • sync
  • 8000 elements
  • just launch the app (or auto launch at the start of the pc) with an already logged account

image

@vtmateos
Copy link
Member

Hi,
Well, the figures are much more reduced than your original report - 19551,7 Mo vs 730,5 Mo. We will keep an eye and forward these feedback so the developer can perform some memory check ups.

@8HoLoN
Copy link
Author

8HoLoN commented Nov 22, 2024

Nop, nothing has reduced!! How can you say that ?!
It increases by 0.6 Mo each second, I just waited less longer to take the screenshot the second time. I can no longer let the app run in the background after the sync happened because the app will use + 20Go of RAM in 2 days of pc usage. (And there's still the 10% cpu usage when the app is in idle)

@vtmateos
Copy link
Member

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.

@8HoLoN
Copy link
Author

8HoLoN commented Nov 22, 2024

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

@vtmateos
Copy link
Member

Hi @8HoLoN ,
We are checking your case and we would like if you can test with latest version from our website (5.9.0) and see if the issue still applies. If reproducible, please send a new log attached to the ticket id GVR-408-63660. You can reply here so we can follow up.
Regards.

@8HoLoN
Copy link
Author

8HoLoN commented Mar 12, 2025

Hi, @vtmateos
I have installed the 5.9.0 version, the problem is still there. Maybe be it is due to the fact that I have recursive folder with symlink (junction) ?

@vtmateos
Copy link
Member

Hi,
Could you send new log files to the ref GVR-408-63660 case? We will check out and start debugging from there.
Thanks for your cooperation.

@8HoLoN
Copy link
Author

8HoLoN commented Mar 20, 2025

Where should I send it ? (I got the ref GVR-408-63660 with a notification email, is there a website associated with it? Which url ?)
Moreover, I checked the log file and it contains sensitives data as the credentials of the user and its private key.

@vtmateos
Copy link
Member

Hi,
Please feel free to remove any message from the log file before sending.
After that, you can either reply to that last email attaching new log files or create a new issue referencing GVR-408-63660. Let me know here when you complete it, so i can follow up your case.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants