Arvid Norberg
Arvid Norberg
I'm planning a few patches to attempt to address this issue. I just landed an improvement to the benchmarks, where it now also measures memory usage (but only on linux...
@djtj85 I take that as a "yes". Can you describe the symptoms?
please give this patch a try: https://github.com/arvidn/libtorrent/pull/6703
> 99% RAM wouldn't be so drastic but i can not open a google chrome or any other apps or games without the system being uncertain. so, you *can* open...
I suspect closing the file is asynchronous, and if that hasn't completed (in the background) by the time the file is attempted to be opened again, it will fail because...
does the file indexing service open files in exclusive mode? i.e. preventing other processes from opening the files if not, the problem would still be that `fopen()` *does* open the...
I imagine it would be simpler to, instead of using `posix_storage` on windows, implement an `win32_storage`. Also single threaded and simple.
> By win32_storage do you mean CreateFile()? Yes. With that API you can specify *share mode* as `FILE_SHARE_READ` and `FILE_SHARE_WRITE`
ok, so *some other* process is opening the file without `FILE_SHARE_READ` and `FILE_SHARE_WRITE` then. Do you agree with that conclusion? Or so you think that test program interferes with itself?
> I posted because CreateFile() behavior no different to other file open functions in Windows (there no fix to gqw issue on libtorrent side). I see, I was under the...