Chocobo1

Should be addressed by PR #92.

Could be related: #6937

> > 1. Data corruption. A power loss and poof go the cached data. Especially when it is gigabytes worth > > Did you try to emulate it (e.g. by...

https://github.com/arvidn/libtorrent/blob/362366481ee567c23e29bf0495ee640d3d66af4a/src/mmap.cpp#L232 Don't know if related, does the opened file supposed to be shared with other processes? or does libtorrent opens multiple handles of the same file? I would expected it...

>actually, every time a file completes, its file handle is closed. I believe this will flush it to disk. From my experience, even the handle is closed the data might...

>Wouldn't it be better to have a periodicity based on the amount of currently downloaded data (since last flushing) so that the size of unflushed data does not exceed some...

>I was just asking about related aspects. Should it not check for files at all at startup and continue running as if the session didn't really break, and only show...

>@Chocobo1 Would you like to work in the development? I can test everything carefully. :) I probably won't have much time to do anything significant.

The option is from libtorrent. It would be best to also file an issue upstream: https://github.com/arvidn/libtorrent/issues

@qbittorrent/bug-handlers Please take a quick look to ensure it is working as intended.