Unfortunately, I’m also on version 3.3.3.40905 and I’m experiencing severe memory leaks with about 3-4 days of uptime.
Running Big Sur 11.0.1 build 20B50 on a 2020 MacBook Pro 13" (4 Thunderbolt 3 Ports).
I have two Google Drive accounts logged in, if that matters.
Restarting Insync will fix the memory leakage temporarily but it always rises back up again.
Hi @hexalellogram,
My apologies for the huge trouble. We’ve deployed some improvements in 3.3.2, but it didn’t cover all the cases, so we’re looking at the recent cases on 3.3.2 and 3.3.3.
Could you send the logs.db and out.txt files to support@insynchq.com? These can be found by clicking the 3 dots on the upper right > Help > Open logs.
Hi,
I’m testing trial version 3.4.1 of Insync.
As I can see, the memory leakage still here. Unfortunately, I cannot afford to have the software with such an issue.
@mia I love what you’ve done with Insync, but I don’t understand why this hasn’t been resolved over the past 18 months. It is easily reproducible so you don’t need more customer logs. There are many code analysis tools can measure all sorts of metrics to I identify the code and operations that could be the source of the memory leak.
I want to leave it running, but find myself starting Insync and then quitting it a few hours later so it doesn’t consume all my systems memory.
My suggestion would be to provide an option to automatically restart the app once per day. This would let people use it without having to manually restart it constantly. It would limit the impact and could be disabled once the leak was resolved.
Hi @Craig_M,
Thank you for your feedback and for taking the time to write to us 
Let me bring this up again with our Mac team and also share your suggestion regarding the auto-restart.
Hi @mia,
Is there an update to this situation? I have two Macs running Insync that are suffering from this issue. One is a Mid 2014 MacBook Pro and the other is a 2020 Mac mini M1. The issue is especially frustrating with the Mac mini as it has only 8GB of RAM and Insync ends up using all of it causing performance issues.
Also—I’ve begun to recently experience an issue (possibly unrelated) where Insync quits on its own a few minutes after starting on my MacBook Pro.
Hi @cdixon1,
Let me forward this to our engineers as it seems like we would need to circle back on this.
Could you please send me a copy of your logs.db and out.txt files so I can check the sudden quitting behavior you’re experiencing?
Hi @miamoran
I will send you the log files shortly, as I just woke my laptop to find Insync not running.
Hi.
Still no reaction on this issue. I submitted the log files on 18th of Feb, 6 months almost passed…
Would be nice to have at least some comments from developers… What brings problems to work on this issue? How can we help? What are the actual plans on it etc.
Hi @Denys_Golubiev! Thank you for following up.
We haven’t been able to deploy a fix on the memory leak issue since the logs that users sent in the past did not provide any leads. 
Additionally, our developers weren’t able to consistently replicate this and needed to focus on other pressing issues that had better leads. We are, however, reinvestigating the issue for our next cycle.
If you could please re-send your latest logs.db and out.txt files to support@insynchq.com, that would be extremely helpful.
I have same problem in my Mac Mini . During synchronisation with Google Drive, the processor is almost 100% utilised. 4-5 Gb of memory is busy .
The computer cannot be used.
If I disconnect Insink, everything is fine.
As far as I understand from your answer this is not a priority for resolution.
After years of use I now think I need to look for other sync software.
Unfortunately.
All the best in solving more important problems.
Hi @caisy,
My apologies for the trouble you’ve been experiencing for a while! As mentioned in my last post, our engineers have once more reprioritized memory leak issues in our upcoming cycle so we can re-investigate the reports we’ve received from our users.
We will inform users as soon as an improvement has been deployed.
Hi @yoshjosh!
Could you please send the logs.db and out.txt files to support@insynchq.com, if you haven’t?
And by any chance, were you doing a large sync when this occurred? Lastly, what cloud storage/s are you using - OneDrive, Google Drive, or Dropbox?
Thanks for the response.
I’m using Google Drive exclusively. Yes, it’s a large sync - approximately 562 GB.
I have sent the files to support@insynchq.com. The logs.db file is 191.1 MB, so I’m not able to send that except as a Google Drive link.
I should add that Insync begins by using 2-3 GB but the memory usage grows and grows over a few days until it uses all available memory.
Hi @yoshjosh! Thank you for providing more information to us. It seems like some cases involve a large sync, while others mention that they’re not doing a large sync at the time Insync’s memory climbed up. The most common denominator we currently see is that it climbs up whenever a user has the machine (and Insync) running for extended periods of time. We’ll check out these discrepancies further and make sure to keep our users updated as soon as a clearer lead and fix are available.
I appreciate your patience!
I have noticed that isdaemon is still running depite insync not running for a few days.
It is consuming 30GB of memory.
Could the issue of memory leak be here?
it’s been two years since the problem was reported, maybe it’s time to spend less time on the forums and spend more time to really fix the problem with the development team? Otherwise, offer memory to your users in the meantime… we pay a license
(sorry for my English)
It is quite amazing that this is still going on. I’ve had to force quit InSync in the last week because of it. What is more amazing is how I am still keen to support the product. But maybe reading this forum is reminding me that its time to look for another option?
Hello, perhaps that is one possible issue - when you notice it could you for now just quit Insync and force-quit the isdaemon process as well before restarting Insync? Thank you and we’re sorry for all the trouble.
