Skip to content
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

Crash on 2GB File Transfer #130

Open
zachongit opened this issue Jan 22, 2022 · 1 comment
Open

Crash on 2GB File Transfer #130

zachongit opened this issue Jan 22, 2022 · 1 comment
Labels
bug Something isn't working need to repro

Comments

@zachongit
Copy link
Contributor

I just watched a 2Gb file get to 99%, then the receiving Diode Drive client crashed. This happened twice in a row (with the file starting back at 0% between). May be related to #110

@zachongit zachongit added the bug Something isn't working label Jan 22, 2022
@dominicletz
Copy link
Member

I guess memory is currently on receival 3x occupied. E.g. for a 2Gb file there are 6Gb of memory consumed. 1) The file as it's being received in fragments 2) The fragments joined together 3) The resulting binary decompressed. To change this we need to change the sync protocol to make the downloads aware of an additional splitting into file chunks. The chunks (e.g. 1mb per chunk) can be stored on disk and retrieved from different peers each (like bittorrent). Then once all chunks have been received the file is being joined & extracted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working need to repro
Projects
None yet
Development

No branches or pull requests

3 participants