File stuck on "Downloading..."

[TheArgentinian]

The log says:

10/14-12:43:50.460213 4348 DTL Transfer update: progress to update = 0, transfer size = 4427183462, transferred bytes = 3334995968, progress reported = 3334995968, progress completed = 3334995968 [speed: 0 KB/s] [mean speed: 0 KB/s] [megaapi_impl.cpp:17160]

10/14-12:43:50.584203 4348 ERR Wrong chunk size for new raid, not padded to RAIDLINE: pos = 3279421440, npos = 3283615744, size = 4194304, RAIDLINE = 80, mod = 64 [raid.cpp:990]

I tried unchecking "Use HTTS for transfers..." and it didn't fix it.

Windows 11

[PJAmerica]

I experienced this last night. Had to shut it down and then re-upload via browser. it never uploaded via MegaSync and disappeared after I relaunched the app.

[technikker]

Which version are you on? I'm having a similar issue, but still haven't found a way to resolve it.

[TheArgentinian]

Which version are you on? I'm having a similar issue, but still haven't found a way to resolve it.

5.6.0.

I had to restart the download to finish it. Wasted gigabytes >:

[sergiohs84]

Thanks for reporting @TheArgentinian.

The issue has been moved to the SDK's repository, since that part of the logic sits on the SDK, not in the app :)

We will investigate your issue. By any chance, do you have full logs covering the download since its start to the moment it gets stuck? Thanks in advance for your help.

[sergiohs84]

A few more questions:

1. Did you change the number of connections in the settings? if so, what's your setup?
2. How many times have you triggered this issue (and what file sizes)?

As a quick workaround, Federico, you can clean the temporary file that stores the data already downloaded. It will result on the transfer having to download again part of the file, but it should solve your problem. The temporary file is name .getxfer with a suffix to identify the transfer. Better to pause the transfer (or close the app) before you proceed to delete the file.

Thanks

[TheArgentinian]

A few more questions:

1. Did you change the number of connections in the settings? if so, what's your setup?
2. How many times have you triggered this issue (and what file sizes)?

As a quick workaround, Federico, you can clean the temporary file that stores the data already downloaded. It will result on the transfer having to download again part of the file, but it should solve your problem. The temporary file is name .getxfer with a suffix to identify the transfer. Better to pause the transfer (or close the app) before you proceed to delete the file.

Thanks

still happening 5.6.1. your workaround is the same as canceling the file and re adding the link. defeats the purpose of the app

MEGAsync.log

[sergiohs84]

Thanks for testing and specially for the log, @TheArgentinian.

I've analyzed your log. It seems there's something wrong upon resuming existing transfers after restarting the app:

12/15-04:28:05.643743 11872 WARN Downloading a file with invalid fingerprint, was: 16281105566:1729825320:FjCrjpidp2yRDBmQXXC7lg:0 [megaclient.cpp:17270]
12/15-04:28:05.648276 11872 DTL  Macsmac calculation advanced to 566755328 [utils.cpp:668]
12/15-04:28:05.648287 11872 DBG  Resuming transfer at 644349952 Completed: 669515776 Contiguous: 644349952 Partial: 0 Size: 16281105566 ultoken: 0 [megaclient.cpp:4068]
12/15-04:28:06.559203 11872 DBG  [CloudRaid::start] CloudRAID started. Initial unused raid connection: 6 [raid.cpp:1214]
12/15-04:28:06.559206 11872 ERR  Wrong chunk size for new raid, not padded to RAIDLINE: pos = 644349952, npos = 650641408, size = 6291456, RAIDLINE = 80, mod = 16 [raid.cpp:990]
12/15-04:29:06.536798 11872 WARN Failed chunk(s) due to a timeout: no data moved for 60 seconds [transferslot.cpp:1382]
12/15-04:29:06.536801 11872 DBG  Transfer failed with error -3 [transfer.cpp:397]

Would it be possible to get a link to the problematic file, so we can debug the code?

In the meantime, I've started a download of a large file and paused in the middle. I'll wait for 48h, so the download URLs expire, and then I'll restart the and try to resume. Maybe that way I can reproduce your issue, guys.

Thanks again for your cooperation.

PS: we have created a ticket for this bug. For reference: SDK-4758