Ticket #1185 (new defect)

Opened 3 years ago

Last modified 4 months ago

Support large file transfers (>4GiB)

Reported by: stickynips Owned by: MarkDoliner
Milestone: Component: AIM
Version: 2.0 Keywords: file transfer size
Cc:

Description

I'm using Pidgin 2.0 on Windows XP SP2. When transferring a large file, nearly 19GB in this case, pidgin misreports the file size in the transfer window. Although it doesn't hinder the file transfer at all, it's a minor annoyance not knowing how much longer you've got left on your transfer.

http://i18.tinypic.com/66dmqfa.png

At the bottom of the picture you will see the file size that Windows reports, as opposed to the "-2033252893 bytes" that Pidgin reports. It seems to me like an integer overflow error. The computer on the other end of the transfer (running Pidgin as well) experienced the same error.

Change History

  Changed 3 years ago by rekkanoryo

  • owner set to MarkDoliner
  • milestone set to 2.0.2

AIM uses a 32-bit unsigned integer to indicate the size of a file. This limits the file size to 4GB. I'd be surprised if you're actually able to send a file larger than 4GB over AIM.

Assigning this to MarkDoliner, who might have more insight or information.

  Changed 3 years ago by rlaager

We must be using a signed integer somewhere, if only the format string, to get a negative number in that display.

follow-up: ↓ 4   Changed 3 years ago by MarkDoliner

  • status changed from new to closed
  • resolution set to fixed

We WERE using a signed conversation in the format string. I fixed that. Hopefully that was the only place.

And yes, AIM uses 32-bit unsigned integers to indicate the size of the file. So you DEFINITELY can't transfer a file bigger than 4GB using Pidgin. If you manage to transfer a file bigger than that using two WinAIM clients then please let me know.

in reply to: ↑ 3 ; follow-up: ↓ 5   Changed 3 years ago by dpadgett

Replying to MarkDoliner:

And yes, AIM uses 32-bit unsigned integers to indicate the size of the file. So you DEFINITELY can't transfer a file bigger than 4GB using Pidgin. If you manage to transfer a file bigger than that using two WinAIM clients then please let me know.

using aim version 6 i was able to transfer a 5 gb tv recording i made, whereas i couldn't with pidgin due to the misreported size (5 gb mod 4 gb ended up reporting it as 1gb)

in reply to: ↑ 4   Changed 3 years ago by dpadgett

upon further inspection, i can send a smaller file from aim 6 to pidgin just fine, but upon trying to send one over 4 gb, pidgin refuses to start the download and it fails. protocol change maybe?

  Changed 3 years ago by MarkDoliner

  • status changed from closed to reopened
  • resolution fixed deleted

  Changed 3 years ago by rprots

I have tried to send 22 GB file (through ICQ). Pidgin says it's 1.88 GB in its file transfer window. And my buddy doesn't even see that I want to send him/her a file. Pidgin crashed(!) when I closed file transfer window.

  Changed 2 years ago by Sim-on

Ticket #6820 has been marked as a duplicate of this ticket.

  Changed 2 years ago by Sim-on

  • milestone 2.0.2 deleted

  Changed 2 years ago by madman2k

using the bonjour protocol, pidgin displayed the right size, but actually only transferred 2GB

  Changed 17 months ago by jruere

Something similar happens to Jabber. From a 3+GB file only 2GB were reported and transferred.

  Changed 4 months ago by salinasv

  • milestone set to 2.7.1

Can someone confirm it happens on newer versions? IIRC it was fixed few weeks ago.

  Changed 4 months ago by darkrain42

  • summary changed from Misreports file size for large file transfers to Support large file transfers (>4GiB)
  • component changed from pidgin (gtk) to AIM
  • milestone 2.7.1 deleted

My reading of this ticket is that it's, at this point, dealing with large file support for AIM, which, AFAIK, is still not supported.

#4514 is possibly related

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!