[BUG] ODrive suddenly stopped syncing completely

[arnwas]

Describe the bug I am using ODrive 0.2.2 (and current git, no visible difference) to sync a google drive to my Ubuntu 19.04 machine. Initially it had around 6 GB, and those synced perfectly. Then via another machine the drive was extended my 5GB additional files, which are accessible via web interface an so on. ODrive does not sync them at all, nor upload local changes since.

To Reproduce

not sure if repeating the above does it. The problem i see may or may not be related to the additional 5GB, this could be by chance. I can't exactly reproduce as i cannot delete the drive to restart.

Expected behavior

Usual syncing.

Additional context

I could find that it gets stuck in app/core/sync.js:1071 while loop due to this.loading being true. I could change it (not knowing what other things that might break):

--- app/core/sync.js +++ app/core/sync.js @@ -1068,7 +1068,8 @@ class Sync extends EventEmitter { }

async finishSaveOperation() {

• while (this.loading || this.saving) { +// while (this.loading || this.saving) {

• while (this.saving) { await delay(20); } } @@ -1167,7 +1168,8 @@ class Sync extends EventEmitter { verbose("Saving sync object"); await this.finishLoading();

• if (this.loading || this.saving) { +// if (this.loading || this.saving) {

• if (this.saving) { return await this.finishSaveOperation(); } this.saving = true;

This leads to some syncing, getting stuck usually after around 100 files somewhere else. (I could not further investigate that yet).

The log only reveals some of my file names (i cannot share those, so i cannot paste the log here), but nothing which even from far resembles an error.

Any help available?

Cheers, Arno

[gitcanzo]

I had the same issue today and, after several re-installs, I might have figured out the cause. This happened to me as well after removing a big folder (~5gb). Odrive stopped syncing, and even after restarting the app or rebooting the system, odrive had basically stopped working.

I could reproduce this issue 3 times. To my understanding it happens when handling large amounts of data, which on my laptop results in 100% RAM usage (8gb in total) of which 75% occupied by cache memory (normally my RAM is used only up to around 30%). When RAM is full, any change to the local Odrive folder will brake Odrive. So I confirm that this bug might be specific to scenarios in which large amounts of data are handled.

I could verify that after clearing the cache with following command: # free && sync && echo 3 > /proc/sys/vm/drop_caches && free oDrive would start working normally again.

So i guess there is something wrong with how odrive is handling memory, and this somehow results in its configuration to completely brake down.

I'm by no means an expert, so sorry in advance if anything is unclear.

[tabodo]

I am using 0.2.2 via Flatpak on Kubuntu 19.04 This has been a persistent problem of the client randomly ceasing syncing. Clearing the caches as above works... temporarily.

[davwong47]

Using 0.2.2 on KDE Neon and having the same issue, but clearing the cache as above does not work. Any more ideas?

[fvguilherme]

What I do here is close the system tray and then reopen ODrive.

[SloCompTech]

I'm also having problems with syncing, a week ago it stopped working. I don't know the reason, but it always shows already synced, but it's not. Could this happen because I have to much files in directory ?