Official eMule-Board: Bug In Xtreme That Cause It Not Respond To Hashset Request - Official eMule-Board

Jump to content

Page 1 of 1

Bug In Xtreme That Cause It Not Respond To Hashset Request Let's hope someone can confirm and fix it

#1 User is offline   Enig123 

  • Golden eMule
  • PipPipPipPipPipPipPip
  • Group: Members
  • Posts: 529
  • Joined: 22-November 04

Posted 22 April 2018 - 10:12 PM

It's been a long time since I first noticed that sometimes a downloading file finished parts without hashset, including ed2k and AICH, which cause red loglines.

After some digging, I found that Xtreme mod is prone to not responding to hashset requests somehow. By reviewing the codes, the 'Xman improved socket queuing' feature along with other socket related improvements seem suspicious.

Though I am still struggling figure out which part of the codes is to blame, it would be great if someone familiar with the mod's codebase can track it down and solve it. After all, Xtreme mod is still very popular.

Edit: The error log is in 'Log' tab, look like "MD4 HashSet not present while veryfing part %u for file %s". It happens when most probably the first connected client is Xtreme mod client, and it failed to response the hashset request, while the following connected clients started to uploading to us. When a part's finished, we found that the hashset is not available yet.

It will last for quite some time, and getting even longer if UDP re-ask always succeeded (since no TCP connections for another round).

This post has been edited by Enig123: 22 April 2018 - 10:46 PM


  • Member Options

Page 1 of 1

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users