Oleg

Solved the problem: In the program in alertloop: ``` final StateChangedAlert stateChangedAlert = ((StateChangedAlert) Alerts.cast(a)); if (downloadedTorrentHandle.getInfoHash().equals(stateChangedAlert.handle().infoHash().toHex()) && stateChangedAlert.getState().swig() == 1) { final torrent_status torrentStatus = downloadedTorrentHandle.swig().status(); final String savePath...

Turn off the internet: final ip_filter ipFilter = new ip_filter(); final error_code errorCode = new error_code(); ipFilter.add_rule(address.from_string("0.0.0.0", errorCode), address.from_string("9.255.255.255", errorCode), ip_filter.access_flags.blocked.swigValue()); ipFilter.add_rule(address.from_string("11.0.0.0", errorCode), address.from_string("127.0.0.0", errorCode), ip_filter.access_flags.blocked.swigValue()); ipFilter.add_rule(address.from_string("127.0.0.2", errorCode), address.from_string("172.15.255.255", errorCode),...

The library does not have a mechanism for writing files in a strict sequence. Since all modern file systems support sparse files Details https://github.com/arvidn/libtorrent/issues/4616

1. search for similar questions before writing 2. Close this issue

Okay :)

@nagyimre1980 Why do you think that?

@constantins2001 Do you have a comparison with version 1.2 of the library?

@stalkerok Are these problems compared to the old version 1.2 of the library? Or are they general problems?

@arvidn Too many changes at one time (1.2->2). Is it possible to roll back the change of disk write type? (memory mapped files) This can increase disk write speed and...

@stalkerok You need to test 1.2 torrents and 2.0 torrents on Url-seeded torrent files. This will rule out problems with other torrent mechanisms. This is pure write speed. Use this...