aMule Forum
English => en_Bugs => Topic started by: Truzzone on January 02, 2007, 05:58:59 PM
-
Hi,
I try the cvs tarball but after 1 days i see always cpu usage at 100%, I'm return to 2.1.3 and the cpu usage are @max 8%.
It's possible to help the developer with gdb backtrace for found the bug?
I compile with wxGTK-2.6.3.3 on gentoo amd64 is this the problem? ?(
What tools you suggest for find the cause of 100% cpu usage? ?(
Best regards,
Truzzone :)
-
Ciao Truzzone!
Hum, you can try the google profiler.
http://code.google.com/p/google-perftools/
But it is normally not so evident what is causing this.
Have you checked if aMule is not re-hashing old files? wx-2.6.3 should be fine, but I have no experience in 64 bits platforms.
Good luck! Hope you can sort it out, and please report!
Cheers!
-
Yes, I've compiled (amuled) of the 26th december CVS tarball too, and have the same issue.
CPU usage is always at 96-98%
- ubuntu 5.10
- wxBase 2.6.3
Don't really know what can I do to help you guys figure it out...gdb? ?(...dunno?!? ?(
best regards,
-
Update to wx 2.8.
-
Hi Kry,
thanks for your reply :D
I suspect this is old wxGTK but on Gentoo wasn't available an ebuild.
I just check bugs.gentoo.org and I find this update (http://bugs.gentoo.org/show_bug.cgi?id=145884) with wxGTK-2.8.0 ebuild.
In the next days I try this ebuild and aMule-CVS with wxGTK-2.8.0 :)
Best regards,
Truzzone :)
-
Ok, I'll test it as soon as I manage to compile wxBase 2.8... I'm having issues on wxBase compilation....
I have to read a little bit more on wxwidgets forums... :P
cheers,