http://bugs.winehq.org/show_bug.cgi?id=6936
Summary: eMule uses 40% CPU when idle, Webinterface does not work Product: Wine Version: 0.9.27. Platform: PC URL: http://mitglied.lycos.de/sdf1014/emule.zip OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: wine-misc AssignedTo: wine-bugs@winehq.org ReportedBy: aollamer@gmx.net
Software used to test: - eMule 0.47c vanilla - Debian latest testing branch, all packages updated, wine 0.9.25 - Ubuntu 6.10, all packages updated, Wine 0.9.27 directly from winehq.org
Machines used: - Debian: P2 400Mhz, 256MB RAM, native Debian installation - Ubuntu: P4 2.8 GHz => running WinXP => running VMWare (384 MB RAM) => running Ubuntu => running Wine - The machines were idle when doing the tests, no other software using CPU time.
Configuration used: - blank eMule configuration, eMule was idle during the tests, no network connection, no downloads, just the plain main menu. - blank Wine configuration, Win2000 mode - the Ubuntu installation was also completely new and unconfigured.
Symptoms: eMule.exe and wineserver use about 40% CPU time together permanently on the Pentium2 box, 70% in VMware on my Pentium4 (both use half of the CPU time). This happens with a completely blank eMule configuration without network connection, downloads or anything. Furthermore, I cannot access the Webinterface because all pages stop loading at some point, i.e. the browser cannot receive the whole data. Waiting for like 5 minutes does not help - the Webinterface does not load and the CPU usage stays constant. Note that the CPU usage is also that high when I have not tried to access the Webinterface yet.
I have always had this problem since I tried eMule on Wine for the first time about one year ago - with all kinds of different Wine/Debian versions etc. updating did not help. The only thing which has changed: In previous wine versions the CPU usage was at 100% always!
Since I've now been able to run the test on the native debian installation and not only in VMware I consider this as a Wine-bug and not a Wine-on-VMware-bug.
Reproducing: Just run a fresh eMule on a fresh Debian/Ubuntu installation.
I have finally also done the effort of running it with WINEDEBUG=all and creating a log. I let eMule run for about 5 minutes so that the startup code should have been finshed and only the debug messages of the infinite loop creating the CPU usage should be in the end of the log now. This indeed seems to be the case, the attached logfile (see URL) is very repetetive. http://mitglied.lycos.de/sdf1014/emule.zip
Feel free to ask me further questions.