See screenshot. IceMon 3.0.0.3 using outrageous memory.
Had to uninstall IceDrive after several years. Now running solely on stable Mega.nz
Sidenote: I rolled back Windows thinking it was the most recent Windows update causing the issue. Very time-consuming to find this still happening.
This answer has zero to do with my issue. I already saw the CPU post which is NOT a RAM issue, as in my case. I specifically included a screenshot of MY issue. And this was the latest version of IceDrive 3.32!!
hi, i spotted the slightly high cpu issue, and although the icedrive team didn’t confirm it, i suspect it was really a memory leak that was causing the slightly high cpu, so it could be relevant. i wasn’t using the sync feature (just the mounted drive). however, fredx’s suggestioni to use the latest version is irrelevant as you’re already using the latest versions that seemed to fix the memory leak when no syncs were defined, but if you’re syncing large data, then perhaps the memory leak is not completely fixed.
have you tried opening a support ticket? not sure if anyone on this forum will be able to help
I haven’t found support to be that ,er, supportive. It’s their way or the highway. Since it is uninstalled, I won’t have any logs to give anyway. The photo should suffice, as I know they look at the forum.
I also ran the Windows Memory Diagnostic which took the better part of my workday, to eliminate one possible cause. The report found no issues with the RAM.
I have a screen shot of another computer running Win 10 with IceDrive version 3.3.1.131 with IceMon 3.0.0.2 running fine. It shows no crazy CPU or Memory use. Glad I did not update despite the constant nag. It is not my main computer so I had to stay with Mega Sync on the one I use daily.
I didn’t always feel this negative, because when IceDrive worked, it worked well. I have used IceDrive for many years, but never fully trusted the platform and lately I cannot use it without a hassle. The Android App is great, however.
Our development team are aware of this issue and an update will be released soon to address this, apologies in the meantime for any inconvenience caused.