Tribler Shutdown problem windows 8.1 and 10. Suddenly after restart a few per cent less than before?

Atention for the shutdown bug in windows 8.1.during the shutdown i get the mention “Errors Occurrend” See the Tribler.exe log for details.

I can’t find this log where should I look?

Log should be at the bottom of the Roaming folder. (To go there easily Windows key + R to open the run/open window, and then type in %appdata%) It’s not in the .Tribler folder, but the roaming folder you go to directly by the %appdata% command.

Hello,

I am having the same issue under Windows 10.
The Tribler.exe.log file contains the following:

ERROR   1466751949.98       community:2579  already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}
ERROR   1466758464.53       community:2579  already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}
ERROR   1466758464.53       community:2579  already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}
ERROR   1466758529.44       community:2579  already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}
ERROR   1466758529.44       community:2579  already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}
ERROR   1466758584.46       community:2579  already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}
ERROR   1466758584.46       community:2579  already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}
ERROR   1466758639.44       community:2579  already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}
ERROR   1466758639.44       community:2579  already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}
ERROR   1466758639.47       community:2868  already seen this indentifier in this batch, previous candidate {192.168.1.20:7759 90.79.25.110:7759} this one {192.168.1.20:7759 90.79.25.110:7759}
ERROR   1466758679.77       community:2868  already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}
ERROR   1466758694.87       community:2579  already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}
ERROR   1466758694.87       community:2579  already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}
ERROR   1466758695.14       community:2868  already seen this indentifier in this batch, previous candidate {192.168.11.7:7759 220.209.225.249:7759} this one {192.168.11.7:7759 220.209.225.249:7759}

7-7 2016 Text adapted and improved.

I have this Shutdown problem only with Windows 8.1 not with Linux.

I have also a strange thing discovered, if Tribler gets shutdown and restart, sometimes Tribler go check the downloads.

When this happens, than it is possible that suddenly one or more download(s) be a few percent less than before. Most time 1% to 5% . I have seen this several times.

Very weird.

Is the “Errors Occurred” a blocking popup from Tribler?
Sorry for being ignorant, I’m a lifelong Linux user…

We should be able to fix that soon. We will work on stable code full-time for coming 10-ish days.
Today the development team split off the code for a new experimental release using Blockchain-based bandwidth credits. Sort of Delft Bitcoins:-) This is just test-driving new features.

Plus we have our credit mining feature from 2013 now finally ready for a first testdrive by you all.
-j

already seen this indentifier in this batch, previous candidate {10.0.0.14:8079 83.82.246.165:8079} this one {10.0.0.14:8079 83.82.246.165:8079}

All harmless warnings, we should probably fix this, and should not trigger an error.

Thank you for your response.

Gladly i wants to report the errors and will come with suggestions, in order to achieve a better program.

Lex Netherlands