-
Notifications
You must be signed in to change notification settings - Fork 1.7k
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sf::Ftp Error Bad Alloc durring Big file transfered ! In sfml-Network #565
Comments
masterWarn
changed the title
sf::Ftp Error Bad Alloc durring Big file transfered !
sf::Ftp Error Bad Alloc durring Big file transfered ! 🐛
Apr 5, 2014
masterWarn
changed the title
sf::Ftp Error Bad Alloc durring Big file transfered ! 🐛
sf::Ftp Error Bad Alloc durring Big file transfered ! In sfml-Network
Apr 5, 2014
Indeed. The full file is stored inside a std::vector, I should find a more clever strategy (like directly writing to the file). Thanks for your feedback. |
This sounds like a job for memory-mapped files. |
Perhaps you could use the std::vector as a buffer ? |
No, no... No need to throw random thoughts, I know perfectly what I have to do ;) |
Ok, thanks :-) ! Thanks for your work, I love SFML ! |
binary1248
added a commit
that referenced
this issue
Apr 30, 2014
binary1248
added a commit
that referenced
this issue
May 6, 2014
binary1248
added a commit
that referenced
this issue
May 6, 2014
binary1248
added a commit
that referenced
this issue
Jul 4, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
When transfering binary file, during big file tranfered (more than 500MB). Application crash :
"terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc"
Crash at line:
myFtp.download("1.1.zip","MyFolder", sf::Ftp::Binary);
Ram is full at 70% of the transfer...
Work fine with little files ( <500MB).
Sorry for my english, I'm beginer.
The text was updated successfully, but these errors were encountered: