[ Outline ] · Standard · Linear+ Anti-eMule files: cause 100% CPU intentionally!, I found 5 diff files who cause that.

[taltamir]

Computer configuration:
eMule Plus version:	1.2
Using proxy:	No
Firewall:	No
CPU:	AMD AlthonXP Burton core 2500+
Memory:	512MB
Operating System:	winXP pro corp SP2 integrated nLite modified
Updated drivers for network and video:	Yes

I found 5 seperate files (with the same name) all of which under 50kb in size (but different sizes individually) which, once completed, cause emule to be stuck at 100% cpu usage (stayed that way over week, surviving restarts and even when i copy pasted all the partial files to a different computer!). The files cannot be deleted from within emule (to delete them, turn off emule and delete the partials from the emule partial directory).

I have kept all the relevant files and they are available here:
http://home.comcast.net/~taltamir/eMule_bug.rar

as you notice there is a part.bad there aswell, to ensure I don't delete something i want I only deleted the .part file leaving the rest after each emule restart. Emule detected the file was missing and did whatever correction it does... I tried restoring those files and the 100% complete files who cause 100% cpu usage came back... I just went ahead and moved them all (with all associated files) to an appropriate directory, compressed them, and uploaded... hope this proves useful in tracking the issue (as I am certain its a malicious instance propagated by anti p2p people)

This post has been edited by taltamir: Sep 16 2006, 10:19

[muleteer]

Most probably. The only reason it might not be there is that the next version is very close to being released and we don't like putting things out without testing them. As you are well aware, our code is significantly different from oMule (short for eMule original or eMule classic) so incorporating functions already there in oMule is not simply a matter of copy/pasting the relevant bits of code.