sledgehammer999

>microsofts own anti virus software. I use avast. >post missing steps to reproduce. 1. Torrent with one big file (at least 10GB) 2. A somewhat fast connection (eg 100Mbps) 3....

It sounds like a lame limitation of the os cache manager to not flush an open file no matter the size/age of its dirty pages. >In the past, forcefully closing...

And if libtorrent is doing memory maps then maybe [FlushViewOfFile()](https://docs.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-flushviewoffile) will help. And the remarks indicate that this is an async call too.

>Did you try to emulate it (e.g. by force terminating qBittorrent process)? qbt was killed immediately. But doing a right-click->Properties on the file didn't show the dialog for a few...

>I'll try to simulate a power loss with a forced VM poweroff. I tried it. Total data loss.

A bit offtopic: @arvidn I know that you have a lot in your plate now, but please consider "finalizing" the Windows portion soon. Aka torrents with many files downloading in...

>I was under the impression that his had been fixed already, in 843074e and 450ded9 The first one just flushes the dirtiest file, which might leave other active files in...

Maybe @arvidn can test this?

@arvidn sorry for not mentioning it already. The issue appears with libtorrent 2.0.5+gitd0f7a09adb

@arvidn to summarise: The latest version of qbt is 4.4.0 and shows the above proxy problem. This version uses libtorrent 2.0.5+gitd0f7a09adb. According to the reporting user the last known working...