Estimated and elapsed time incorrect

Posts: 28 · pollotedax 14 Oct 2013, 15:45

Hi,
I'm having incorrect values for estimated and elapsed time with version 5.22, even negative values.
The speed numbers in the left top corner of both graphics are incorrect, too.
I'm having right now -153GB/seg and -30458 elements/seg.
The last three syncs were also bad.
They are very big ones but never saw it before.

Thanks !

Posts: 28 · pollotedax 17 Oct 2013, 06:02

Could it be at 00:00 when the day changes?

Posts: 7058 · Zenju 17 Oct 2013, 10:38

The negative numbers for speed (bytes and items per sec) must be a follup-up issue due to a problem with elapsed time. Are you able to reproduce this behavior?

Posts: 28 · pollotedax 17 Oct 2013, 19:57

I think so.

My last 5 sync jobs were bad. There are big ones. The begining is ok, but in certain moment gets wrong.

I'm quite sure the numbers will be bad again if I launch any of those jobs but don't know the exact moment.

Some of them took up to 33 hours to finish so my think is the day change at 00:00 may affect, but is only an idea

Thanks.

Posts: 7058 · Zenju 18 Oct 2013, 12:50

This is very likely caused by a timer overflow considering the length of 33 hours: the wxWidgets timer class is using high-precision timers which is probably overkill in this scenario.
Do you happen to have a picture of one of the progress graphs?

Posts: 7058 · Zenju 18 Oct 2013, 14:17

I've implemented an internal timer that depends on the system UTC time. Please confirm that this solves the timer overflow problem for you:

[404, Invalid URL: http://freefilesync.sourceforge.net/FreeFileSync_5.23_beta_Windows_Setup.exe]

Posts: 28 · pollotedax 18 Oct 2013, 14:43

Thanks so much. I'll try.
I created a super big-job with all the jobs and is currently runing.
When finished, I'll paste an image and re-run the same job with the 5.23 beta.

Posts: 28 · pollotedax 20 Oct 2013, 16:41

Failed, I launched it and just get this error when the comparison finished and is gonig to show the comparison result window.

It is a 6.646.000 files job.

Is the first time I get this error.

Posts: 28 · pollotedax 20 Oct 2013, 16:51

It was manual. I relaunched it as a ffs_batch job.

It takes one hour to compare.

Posts: 7058 · Zenju 20 Oct 2013, 17:02

Could it be an out of memory?

Posts: 28 · pollotedax 20 Oct 2013, 17:50

Don't think so. Maybe it was casual.
Now it finished comparing and is copying....

Number seems good.

Posts: 28 · pollotedax 20 Oct 2013, 18:36

All finished good with no negative numbers, so the correction seems to be good.
Thanks again!

The job takes shorter than usual because it is synced but will inform here about any changes.