Opened 9 years ago

Last modified 6 years ago

#5657 new Bug report

Elapse time incorrect for single download 1 hour or more

Reported by: Ross Howatson Owned by:
Priority: normal Component: FileZilla Client
Keywords: elapsed time Cc: rosshowatson@…, key-FileZilla2606-contact@…
Component version: Operating system type: Windows
Operating system version: XP Pro SP3

Description

When doing a large download which takes more than 1 hour the elapse time does not show the hour.

Attachments (2)

FileZilla.JPG (180.8 KB) - added by Ross Howatson 9 years ago.
Incorrect Elaspe time (1:20:07) shown.
screenshot.png (188.1 KB) - added by Derric Atzrott 7 years ago.
Screenshot of FileZilla from ~2 hours after download began

Download all attachments as: .zip

Change History (11)

comment:1 Changed 9 years ago by Tim Kosse

Status: newmoreinfo

Got a screenshot?

Changed 9 years ago by Ross Howatson

Attachment: FileZilla.JPG added

Incorrect Elaspe time (1:20:07) shown.

comment:2 Changed 7 years ago by Alexander Schuch

Do you still have that problem with a current version of FileZilla?

comment:3 Changed 7 years ago by Derric Atzrott

Status: moreinfonew

Someone at the company I work for just reported this issue to me. Figured I'd say that it still appears to happen in 3.5.3.


<User> fascinating
<User> filezilla seems to keep a very poor record of time elapsed
<Me> Oh?
<User> apparently 1:45 has elapsed since we started
<Me> Did the download stop for some reason?
<User> but that's not one HOUR and 45 MINUTES, it's 1 minute, 45 seconds
<Me> Filezilla also keeps track of time for individual files I think, not sure if that might make the difference?
<Me> While I was at Wikimania I also discovered my laptop at least was set up to cut off network connections if it was closed (something I have since fixed).
<Me> So that could be it too perhaps.
<Me> That or Filezilla really is just terrible at time-tracking. In which case someone should file a bug-report with them so it gets fixed.
<User> well, this is version 3.5.3
<User> so it's possible that there's a new version
<User> but I didn't close down any network connections or anything
<User> what I DID do, was walk away from it, BUT that seems very precient of it


OS: Windows Server 2008 R2 Standard (64-bit)
FileZilla Version: 3.5.3
Reported Elapsed Time: 0:12:00
Actual Elapsed Time: 2:00:00+

Changed 7 years ago by Derric Atzrott

Attachment: screenshot.png added

Screenshot of FileZilla from ~2 hours after download began

comment:4 Changed 7 years ago by Derric Atzrott

Should have put this in the first comment, but it might be worth noting also that the conversation between the user and myself was an hour before the screenshot was taken, so the problem definitely wasn't a temporary one.

comment:5 in reply to:  description Changed 7 years ago by Ross Howatson

Replying to RossHowatson:

When doing a large download which takes more than 1 hour the elapse time does not show the hour.

New:
Not sure if you want me to update this problem but I will.

Yes I have Filezilla version 3.5.3 loaded.

Yes I can duplicate the problem again. I may have to wait 2+ hours but it happens.

Running Windows XP SP3 fully patched (as of July 10th) with Norton Antivirus loaded.

Wired connection to Linksys E1000 router to Bell Canada modem. Connection is not dropped at either local system or Bell Canada.

Download a single 20-30 GB file and it will report incorrect elaspe time. When finished the download it can take minutes to hours before the download sitting at 100% moved from the Queued files to Successful transfer.

Hopes this helps.

comment:6 Changed 7 years ago by Ross Howatson

Cc: rosshowatson@… added

I tried to duplicate this problem today using Filezilla 3.5.3 using a very large download and let it run for more than 5 hours. It reported the correct time during the download.

The problem appears to have been fixed and I thank all who put effort into it.

If others can duplicate the problem on other platforms then please attempt. If you cannot duplicate the problem on other platforms do I have to close the problem?

comment:7 Changed 7 years ago by Derric Atzrott

As I mentioned earlier, the problem appears duplicable in Windows 7. I've not yet tested this myself (still need to find a large enough file), but one of the other employees at the company I work for has been able to.

Duplicating this problem is on my plate for tomorrow. I'll give an update then as to whether or not I could manage to duplicate it.

comment:9 Changed 6 years ago by keyman

Cc: key-FileZilla2606-contact@… added
Keywords: elapsed added; elapse removed

I am also seeing this behavior on version 3.7.3.
On multiple downloads and uploads the elapsed time never shows anything for hours other than "00".

I do not recall this issue being there previously, but it is possible that I just did not see it.

FileZilla Client


Version: 3.7.3

Build information:

Compiled for: i586-pc-mingw32msvc
Compiled on: x86_64-unknown-linux-gnu
Build date: 2013-08-07
Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2)
Compiler flags: -g -O2 -Wall -g -fexceptions

Linked against:

wxWidgets: 2.8.12
GnuTLS: 3.1.11
SQLite: 3.7.16.2

Operating system:

Name: Windows XP (build 2600, Service Pack 3)
Version: 5.1
Platform: 32 bit system

comment:11 Changed 6 years ago by Ross Howatson

Currently I cannot duplicate the problem. We upgraded Internet speed and now rarely have downloads of hours in length.

Note: See TracTickets for help on using tickets.