Hi
I am using insync headless since years on an Arch Linux server with 16GB RAM.
Since a couple of weeks I saw insync eating lots of memory and then getting the OOM Killer. I increased the swap partition to 64GB and now it seems that insync survives after a reboot by first filling up a shit load of RAM and eventually settles down with a consumption of about 25% of the available memory.
I am pretty sure, this should not be like that. How can I investigate what the issue is and/or fix this?
I see the same problem
Could you send your logs.db and out.txt files to support@insynchq.com with the link to this post? We’ll look into the possible cause of a spike in RAM usage so we can address this accordingly.
May I also know if there was a large ongoing sync at the time this behavior began or was Insync just running in the background?
Thank you!
There was no large ongoing sync happening.
I removed insync from my computers resulting in a whole data migration to a cloud which works better with linux.
The ongoing insync instabilities are not accesptable.