View Issue Details

IDProjectCategoryView StatusLast Update
0000299TeraCopy(No Category)public2018-01-15 03:42
PrioritynormalSeveritymajorReproducibilityhave not tried
Status newResolutionopen 
Product Version3.26 
Target VersionFixed in Version 
Summary0000299: TeraCopy shows vastly incorrect moving speed and wrong (doubled) number for moved bytes
DescriptionYou can see the screenshot. I was moving files from my PC to a NAS, and the average speed I reach is 50-100MB megabytes/sec. Obviously numbers in the 100-250 gigabytes/sec that I was getting were way wrong.

Also obviously it makes no sense for the progress on right to show "150.81 GB moved out of 107.74 GB".
Steps To ReproduceI have no exact steps to reproduce, I can only give as many details about what I did as possible.

- Source: Windows 10 PC's hard drive (NTFS)
- Target: Synology NAS DS416j, SMB shared folder
- Network type: Gigabit ethernet, average speed from Windows to NAS 0000081:0000050-100 megabytes per second.
- Type of content: 107 GB of media files (videos, music, etc.). The files were static during the operation, no files have changed.
- I've been pausing the transfer and starting other TeraCopy transfers, then resuming.
- I've ticked the "verify" checkbox about 10-20% into the transfer.
- The wrong numbers seem to have appeared after one of the times I *resumed* that particular transfer.
- The transfer speed reported was in the range 50-250 gigabytes per second.
- When the transfer completed (seemingly successfully), it showed "32 MB/s" average speed at the very end, which unlike previous numbers seemed plausible and probably correct.
- When the transfer completed, it was showing that it has moved "214.08 GB / 107.74 GB". The two numbers should match. Notice the first number is almost exactly twice the second, but NOT EXACTLY TWICE. Weird.
TagsNo tags attached.
OSWindows 10
OS Version64 bit




2017-12-12 18:44


TeraBug.jpg (30,323 bytes)
TeraBug.jpg (30,323 bytes)


2017-12-15 17:08

reporter   ~0000206

I have also noticed this when moving files. When it verifies the amount of data gets counted when it's read again.


2018-01-11 18:36

reporter   ~0000213

FWIW, it doesn't happen when showing the large progress bar.


2018-01-15 03:42

reporter   ~0000214

Noticed this as well. At least data consistency isn't bugged.

Issue History

Date Modified Username Field Change
2017-12-12 18:44 johncamran New Issue
2017-12-12 18:44 johncamran File Added: TeraBug.jpg
2017-12-15 17:08 andyo Note Added: 0000206
2018-01-11 18:36 andyo Note Added: 0000213
2018-01-15 03:42 edmundo096 Note Added: 0000214