So this is not good. A ridiculous amount of memory usage.
@Mac_Sims Hi! This is definitely not good as it is hogging your resources! Does the memory leak happen even when Insync is running idle (i.e. no sync activity)?
It happens at idle, but at a much slower rate than when it is syncing files/folders. I ended up just restarting the app every day, as by the end of the day I would hit 10+ GB usage. It’s a very badly coded piece of software. Since this has been an issue for years as can be seen throughout the forums, I suspect their main mac coder has resigned some time ago and the app has been left to languish, with some minor changes made but nothing significant to try fix this problem.
Hi @Rob_euk!
I am terribly sorry to hear that you’ve needed to restart Insync every day due to the memory leak issue.
Our Mac Team has revisited this long-standing issue in the past, but one main factor with these kinds of issues is its level of replicability. We initially had a promising lead regarding Insync’s interaction with Time Machine, but unfortunately after the improvements were released, the issue eventually resurfaced. 
Another user shared that the memory leak happens with Carbon Copy Cloner task running - is there any chance you have this on your machine as well?
No I do not have carbon copy cloner installed. I previously sent through logs as well so you can see the data dump.
@Rob_euk, thank you for confirming! I was able to trace the logs that you previously sent to my teammate.
Rest assured that we will continue to look into this memory leak issue so we can finally put it to rest. Constantly restarting Insync is definitely not sustainable (especially if you have to wait for it to finish scanning, you’re in the middle of a large sync, etc).
Thank you for your patience!
If this problem is every fixed after 1 year having had the license, will we get a free update, or will we have to purchase another license to get the problem fixed?
Hi @Rob_euk, assuming that this is the license found on https://www.insynchq.com/pricing, then you do not need to purchase another one when the memory leak issue has been fixed in a new version. 
The once-paid license includes version upgrades already. Hope that helps!
Experiencing this as well syncing with Google Drive on Macbook Pro Intel. It was an issue with MacOS 14 and still an issue 15.0 Beta.
Hi @harty83, could you confirm if this issue persists even when Insync is running idle (i.e., no files are being synced)?
It seems to be over time. Ill notice my Mac struggling, check activity monitor, and its always insync taking up significant amount of RAM. When I check, it’s not actively syncing. So ill close it and then over time it goes back to using up a lot of ram.
1 Like
@mia I’m also experiencing this. I always have it running in the background and I have to kill the process every so often otherwise all of my memory gets taken up. I just had to kill it at 70GB of ram, which is crazy. There’s clearly a memory leak somewhere and honestly, given the age of this thread, it’s taking an unacceptably long time for this to be fixed
Hi @olly_rennard, thanks for tagging me on this related discussion. We fully acknowledge that this long-standing issue has plagued many of our Mac users. Unfortunately, this issue has been quite difficult to replicate which has been a huge factor in the delays of providing a fix. We truly apologize for that and rest assured that I’ll continue to raise this to our engineers so we can allocate resources to this in the near future.
@mia I’ve been in touch with support in the past on this ongoing issue. I’ve had this memory leak issue on every Mac device I’ve run Insync on. I recently added a new M4 mini to the mix and I am experiencing the same issue. In fact I woke the Mac up this morning to find that Insync was unresponsive and using 45GB of memory. This is a new record for Insync memory usage on any of my Macs. This is after about 3 days of the Mac sitting idle not syncing anything. Supremely annoying. This has been going on for several years now and it’s shocking that the issue hasn’t/can’t be resolved.
@FredHanselmann Indeed, this macOS issue has been plaguing our users for a while now and I truly understand how annoying and frustrating it has been. While memory leak has been a difficult issue to replicate (where replicability is a big indicator of fixing the bug), rest assured that we will continue to circle back to this issue whenever our resources permit us to do so.
Thank you so much.
Happens on mine too, version 3.8.7.50505 on Apple Silicon Mac.
If nothing else could we get a popup that tells us when memory is over a certain amount? Killing the app every so often isn’t that annoying but memory usage climbing in the background without me realising until everything grinds to a halt is
1 Like