Arvid Norberg

it depends on what you mean by "completed". I believe they must all have been downloaded and hash checked before `is_seeding` is true. But they may not yet have been...

I take it the 64 bit build does not have this problem, right?

first step at fixing this: https://github.com/arvidn/libsimulator/pull/68

I simplified your patch a bit and added a test: https://github.com/arvidn/libtorrent/pull/7027 Would you mind giving it a try to make sure it still works?

that's quite a pessimization. I'd like to avoid it if possible. It's a gnarly situation though, it's a data race in some cases, but not in the common case.

@FloatingMind12 what version of libtorrent are you using? Do you see any evidence that files are copied or duplicated other than the error message (`ENOSPACE`)? It's possible the out-of-disk error...

I'm leaning towards agreeing with @AllSeeingEyeTolledEweSew . There needs to be some limit of scope of features in libtorrent (which already is very large, perhaps a bit too large). I...

presumably the tool would only be asked to defragment the file that just completed downloading, which is knowable outside of libtorrent. There's even an alert when a file completes.

> Are you talking about the option "run external program on download completion"? not specifically. I'm talking about the option of running a program on receiving the `file_completed_alert`

it's messages carrying information from the bittorrent engine to the client. http://libtorrent.org/reference-Alerts.html#file_completed_alert http://libtorrent.org/reference-Session.html#set-alert-notify-pop-alerts-wait-for-alert