DCC drops out after 30Mb

[GoogleCodeExporter]

What steps will reproduce the problem?
1. join #horriblesubs on irc.rizon.net
2. request a file with /CR-FRANCE|NEW xdcc send #number

What is the expected output? What do you see instead?
Transfer halts after 28-30Mb

What version of the product are you using? On what operating system?
Snapshot 13/3/2015 running on debian (raspberry pi)

Please provide any additional information below.
Issue does not occur when sending files from my pc via dcc 

Original issue reported on code.google.com by client...@gmail.com on 13 Mar 2015 at 4:45

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The same issue is present on old pircbot builds, (before pircbotx)

Original comment by client...@gmail.com on 13 Mar 2015 at 5:03

[GoogleCodeExporter]

Issue seems RPI specific, maybe due to ram use?

Original comment by client...@gmail.com on 13 Mar 2015 at 2:58

[GoogleCodeExporter]

Indeed the issue was the buffer size being to big, might be worth calculating 
it on the amount of free ram available 

Original comment by client...@gmail.com on 13 Mar 2015 at 3:12

[GoogleCodeExporter]

Just tested sending a 4GB file to PircBotX on the latest snapshot and didn't 
get any errors or dropouts.

By default there is a 1024 byte buffer. RecieveFileTransfer relies on 
RandomAccessFile to do any buffering as there isn't a flush() method exposed. 
I'm not sure what I can do on my end. 

Did you get any exceptions? What was your buffer size? 

Original comment by Lord.Qua...@gmail.com on 4 Apr 2015 at 10:07

• Changed state: Accepted

[GoogleCodeExporter]

no exceptions, it would just stop and time out the transfer
currently using a 10240 byte buffer which seems to make it not stop halfway, 
quite a odd bug in all honesty setDccTransferBufferSize(1024*10)

Original comment by client...@gmail.com on 4 Apr 2015 at 11:16

[GoogleCodeExporter]

Wow that is odd. Anything in dmesg or /var/log/syslog?

Original comment by Lord.Qua...@gmail.com on 5 Apr 2015 at 12:36