238853 - FTP fails to copy files over 4,294,967,295 bytes (4 GB)

Status: RESOLVED WORKSFORME

(Core Graveyard :: Networking: FTP, defect)

Description

[Papa Smurf]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113

Mozilla only copies the first 4,294,989,276 bytes of the file.

FTP://

Mozilla 1.6 FTP browser also only lists file sizes up to 4,294,967,295 bytes.
Anything larger than that it doesn't list a size.


Additional problems related to this:
When the time left field hits 0, Mozilla starts counting using negative numbers.
  Ex: -13 minutes 50 seconds is shown as "0-13:0-50"
The status KB left will overflow, and the percentage will become negative as 
well.


Verified that this isn't a problem with the server using a 4,613,734,400 byte 
file and IE's FTP.

I haven't had a chnce to try this in 1.7b yet.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Expected Results:  
Downloaded the entire file.

Comment 1

[Jeff Walden [:Waldo]]

Possible dup candidates:
bug 232371 - the second issue mentioned here is that bug
bug 184452 - more general, might cover first part?

Leaving for more qualified dupification...

Comment 2

[benc]

-> NEW,
real problem, lets let the module owner decide how to manage the incoming bugs
and mark them...

Comment 3

[benc]

Did this problem ever happen in versions before Mozilla 1.6? It probably should
have.

Comment 4

[Christian :Biesinger (don't email me, ping me on IRC)]

*** Bug 249627 has been marked as a duplicate of this bug. ***

Comment 5

[Matthias Versen [:Matti]]

*** Bug 276486 has been marked as a duplicate of this bug. ***

Comment 6

[Dave Townsend [:mossop]]

*** Bug 302347 has been marked as a duplicate of this bug. ***

Comment 7

[Mime Čuvalo]

This 4GB limit size is a problem that I've run into in developing FireFTP.  It seems the problem lies with nsIBinaryOutputStream.writeBytes:

Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIBinaryOutputStream.writeBytes]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://fireftp/content/js/connection/dataSocket.js :: anonymous :: line 258" data: no]

Comment 8

[Doug Turner (:dougt)]

mass reassigning to nobody.

Comment 9

[Makoto Kato [:m_kato]]

Although I tests on the latest m-c, it works fine.  I think this issue is fixed by bug 283489 and bug 264599.

Reporter, could you test this issue on latest trunk?  If no response, I will close this as works for me.

Comment 10

[Mime Čuvalo]

Still not working (I made comment #7 ):
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIBinaryInputStream.available]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://fireftp/content/js/connection/dataSocket.js :: anonymous :: line 449"  data: no]

The error is different this time at least but still broken.  This prevents FireFTP from transferring files over 4gb still.

Running Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729)

(by the way, for reference, to create large files on the fly):
Linux:
dd if=/dev/zero of=4gbfile bs=1024 count=4194304

Windows:
fsutil file createnew d:\temp\4gbfile.txt 4294967296

Comment 11

[Makoto Kato [:m_kato]]

Mime, is your commet is FireFTP?  If so, you should talk with FireFTP developer.
This bugzilla is for mozilla products, not FireFTP.

Comment 12

[Mime Čuvalo]

(In reply to comment #11)
> Mime, is your commet is FireFTP?  If so, you should talk with FireFTP
> developer.

Hah, I am the developer of FireFTP.  And FireFTP uses the Mozilla socket API's to transfer files over the network.

related bugs:
https://bugzilla.mozilla.org/show_bug.cgi?id=184452
https://bugzilla.mozilla.org/show_bug.cgi?id=215450

Comment 13

[Makoto Kato [:m_kato]]

(In reply to comment #12)
> (In reply to comment #11)
> > Mime, is your commet is FireFTP?  If so, you should talk with FireFTP
> > developer.
> 
> Hah, I am the developer of FireFTP.  And FireFTP uses the Mozilla socket API's
> to transfer files over the network.

This bug description is that Mozilla without extension cannot handle over 4GB file.  If we don't use FireFTP, we can handle it now.

I think that your issue is about interface limit of nsIBinaryInputStream.  So you should file new bug for it.  We should not discuss multiple issues in one bug entry.

Comment 14

[Mime Čuvalo]

Opened up bug 507312.

Comment 15

[Makoto Kato [:m_kato]]

Not reproduce on 3.5 and trunk.

If you can reproduce this on trunk or 3.6a1, please file a bug again with repro step.