HedgehogInTheCPP Posted February 17, 2016 Report Share Posted February 17, 2016 Good day! All releases since 3.4.5.41628 and ending 3.4.5.41865 fall (crash) or hang (most likely deadlock) when using isp.peer_policy_* OS: Windows 7 x64 SP1 with all updates. But actually it does not matter, the problem is in the code responsible for processing content isp.peer_policy_url file or in code, which is based on the data of the file change the values in the collection with peers. Quote empirically found out the reason Crush all builds starting with 41628 and ending with the last current 41811. 1. settings.dat and resume.dat made clean 2. run the client - works. no one setting is touched 3. unloaded client reload - works. I set the path to the local btpolicy.xml. I changed nothing anymore. 4. unloaded client reload - through crash a few seconds yet I can not understand that it is in btpolicy.xml not like it, because Delete / Edit Ranges sometimes leads to a fall, sometimes not (client stupidly hangs tightly). original: http://rutracker.org/forum/viewtopic.php?p=70028607#70028607 Quote Cool, I have this bug is repeated today just changed the server configuration for the feasts and the client some time after it has downloaded crashed. original: http://rutracker.org/forum/viewtopic.php?p=70031562#70031562 Quote if I "feel" that you can not wait, but simply reset isp.peer_policy_date and isp.peer_policy_expy, and it works in real time, the client will re-read the file.It is said that if a single range of a file, it does not happen Crush. but two or more - falls. original: http://rutracker.org/forum/viewtopic.php?p=70032925#70032925 Please fix! P.S. Please write me if you need more information. Best Regards! Link to comment Share on other sites More sharing options...
hardhouse Posted February 21, 2016 Report Share Posted February 21, 2016 build 41821 as always crushes after startup (with filled isp.peer_policy_url) Link to comment Share on other sites More sharing options...
HedgehogInTheCPP Posted February 26, 2016 Author Report Share Posted February 26, 2016 build 3.4.5.41865 also buggy. The problem is not fixed Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.