Rclone crash while uploading files

What is the problem you are having with rclone?

**Sonarr causing rclone to crash via fuse, only happens with torrent client, nzb is moving files to drive correctly.

What is your rclone version (output from rclone version)

rclone: Version "v1.56.0-beta.5480.9ff6f48d7"

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Windows 10 x64

Which cloud storage system are you using? (eg Google Drive)

Google Drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

mount --vfs-cache-mode writes --log-level DEBUG gcrypt: X: --config "C:\rclone\rclone.conf" --log-file C:\rclone\rclone.txt --transfers 20  --multi-thread-streams 20

The rclone config contents with secrets removed.

[gdrive]
type = drive
client_id = [secret]
client_secret = [secret]
scope = drive
root_folder_id = [secret]
token = [secret]
 
[gcrypt]
type = crypt
remote = gdrive:/crypt
filename_encryption = standard
directory_name_encryption = true
password = [secret]
password2 = [secret]

A log from the command with the -vv flag

https://pastebin.com/5ZU6FuYU

I was previously getting the same sort of crash but it was due to a bad memory stick which I identified and removed. Tested ram with memtest and windows tool and RAM memory is not corrupted.

perhaps try latest stable rclone, not beta?
what version of winfsp?

Thanks for the response, same with latest stable version also. WinFSP 2021 is on 1.9.2.21096.

so you had bad ram, replaced the ram and get the exact same error?

Yes, have 4 16gb dimms, 1 was bad removed it and its out for rma. This was the older thread Uploading via rclone crash

New log with stable 1.5.5.1 2021/05/05 12:29:24 DEBUG : /: Getattr: fh=0xFFFFFFFFFFFFFFFF2021/05/05 12:29: - Pastebin.com

The file stays at 0bytes on the remote drive after the crash

New log more details

Oddly enough the files that go through SabNZBD get imported over just fine.

That looks like bad memory/hardware. You can memtest it and see if something is going on.

Thanks for the response, spent over 3 days scanning for bad memory, it passes on memtest now.

Motherboard/CPU as that backtrace looks like bad hardware.

Same thing happens on laptop which has no bad memory. Thanks

Do you have a log from the second device?

Yes, I'll upload soon, thanks for the quick responses.

Here you go same issue different hardware

Thanks

That looks to be just the bottom of the log. Do you have the full log?

top part of the log 2021/05/05 13:38:31 DEBUG : Using config file from "C:\\rclone\\rclone.conf"20 - Pastebin.com

After sitting there a while trying to write to the remote storage it will crash again. More logs:

Just before the crash this entry stood out:

2021/05/05 14:10:06 DEBUG : ൝: Release: fh=0x0

I'm going to try an older version of Rclone, this behavior started a while ago and it was working but stopped after I started using 1.50+ I believe. Will test it out.