View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001740aMulepublic2014-09-12 13:582014-09-25 11:45
Reporteradri58 
Assigned To 
PriorityurgentSeverityblockReproducibilityalways
StatusnewResolutionopen 
PlatformGNU/LINUXOSDebian amd64OS Version7 - Wheezy
Product VersionSVN 
Target VersionFixed in Version 
Summary0001740: aMule 100% CPU Usage
DescriptionHi

As soon as I open aMule it starts consuming 100% of CPU until it freezes the system.

Thanks in advance for this awesome piece of software.
Steps To ReproduceJust open amule and after few seconds it will freeze the PC
Additional InformationThis is the exact version:

aMule SVN compiled with wxGTK2 v3.0.1 (Snapshot: rev. 10835) (OS: Linux)

If it helps, I have detected that known2_64.met starts growing in size but probably it is the normal behaviour.
TagsNo tags attached.
Fixed in Revision
Operating SystemDebian 7 Wheezy amd64
Attached Files? file icon logfile [^] (4,419 bytes) 2014-09-12 13:58 [Show Content]
? file icon amule.conf [^] (4,288 bytes) 2014-09-12 14:00

- Relationships

-  Notes
(0003638)
GonoszTopi (administrator)
2014-09-14 12:28

First of all, aMule is *NOT* yet ready for wx-3.x

However, I'd like to know a bit about the circumstances. Is it possible that it's just rehashing your shared files and that's the 100% CPU you experience (guessing from the growsing size of know2_64.met)? What happens if you leave it working for a while (or remove your shared files so that it doesn't have anything to rehash)?

Did you build aMule yourself or is it a debian package you use?
(0003639)
adri58 (reporter)
2014-09-14 15:57

It is the aMule provided by Debian SID (2.3.1+git1a369e47-1)

According to Debian changelog, WX 3.0 support has been added:

* New upsteam GIT snapshot repository; add support to WX 3.0; Closes: #751241
* debian/patches/*
    - refreshed, removed patches merged upstream
* debian/control
    - upgraded b-d to WX 3.0
* debian/watch
    - mangle Debian version for Git snapshot

So the problem might be from Debian? It seems that WX 3.0 support was added because of this bug (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751241 [^])

And if aMule has nothing to rehash it won't freeze the system, so that is the problem.

Anyway, I could try downgrading to the previous version.
(0003640)
nsaspy (reporter)
2014-09-15 11:53

i think this is same bug than this http://bugs.amule.org/view.php?id=1725 [^]

my strong guess that freeze is caused by memory hog.
meaning: it allocates more and more memory before its run out.
(0003643)
adri58 (reporter)
2014-09-15 22:21
edited on: 2014-09-17 16:28

I have tried downgrading to aMule 2.3.1 compiled with wxGTK2 v2.8.12 but I get this error:

(amule:28714): GdkPixbuf-WARNING **: Error loading XPM image loader: El tipo de imagen «xpm» no está soportado

(amule:28714): Gdk-CRITICAL **: IA__gdk_drawable_get_size: assertion 'GDK_IS_DRAWABLE (drawable)' failed

(amule:28714): Gdk-CRITICAL **: IA__gdk_drawable_get_depth: assertion 'GDK_IS_DRAWABLE (drawable)' failed

(amule:28714): GdkPixbuf-WARNING **: Error loading XPM image loader: El tipo de imagen «xpm» no está soportado

(amule:28714): Gdk-CRITICAL **: IA__gdk_drawable_get_size: assertion 'GDK_IS_DRAWABLE (drawable)' failed

(amule:28714): Gdk-CRITICAL **: IA__gdk_drawable_get_depth: assertion 'GDK_IS_DRAWABLE (drawable)' failed

(amule:28714): GdkPixbuf-WARNING **: Error loading XPM image loader: El tipo de imagen «xpm» no está soportado

(amule:28714): Gdk-CRITICAL **: IA__gdk_drawable_get_size: assertion 'GDK_IS_DRAWABLE (drawable)' failed

(amule:28714): Gdk-CRITICAL **: IA__gdk_drawable_get_depth: assertion 'GDK_IS_DRAWABLE (drawable)' failed

(amule:28714): GdkPixbuf-WARNING **: Error loading XPM image loader: El tipo de imagen «xpm» no está soportado

(amule:28714): Gdk-CRITICAL **: IA__gdk_drawable_get_size: assertion 'GDK_IS_DRAWABLE (drawable)' failed

(amule:28714): Gdk-CRITICAL **: IA__gdk_drawable_get_depth: assertion 'GDK_IS_DRAWABLE (drawable)' failed

--------------------------------------------------------------------------------
A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
    http://forum.amule.org/index.php?board=67.0 [^]
If possible, please try to generate a real backtrace of this crash:
    http://wiki.amule.org/index.php/Backtraces [^]

----------------------------=| BACKTRACE FOLLOWS: |=---------------------------
Current version is: aMule 2.3.1 compiled with wxGTK2 v2.8.12
Running on: Linux 3.16-1-amd64 x86_64

[2] wxMutexLocker::~wxMutexLocker() in amule[0x46288f]
[3] wxFatalSignalHandler in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f9f7ee1354c]
[4] ?? in /lib/x86_64-linux-gnu/libpthread.so.0[0x7f9f80b0f8d0]
[5] wxDataObjectSimple::~wxDataObjectSimple() in amule[0x50d78e]
[6] wxTimer::IsRunning() const in amule[0x56667b]
[7] wxMutexLocker::~wxMutexLocker() in amule[0x465549]
[8] std::vector<unsigned short, std::allocator<unsigned short> >::_M_insert_aux(__gnu_cxx::__normal_iterator<unsigned short*, std::vector<unsigned short, std::allocator<unsigned short> > >, unsigned short const&) in amule[0x503144]
[9] wxStringData::Unlock() in amule[0x4f4c27]
[10] CryptoPP::ClonableImpl<CryptoPP::SHA1, CryptoPP::AlgorithmImpl<CryptoPP::IteratedHash<unsigned int, CryptoPP::EnumToType<CryptoPP::ByteOrder, 1>, 64u, CryptoPP::HashTransformation>, CryptoPP::SHA1> >::Clone() const in amule[0x48eb24]
[11] std::vector<unsigned int, std::allocator<unsigned int> >::operator=(std::vector<unsigned int, std::allocator<unsigned int> > const&) in amule[0x4c3617]
[12] CryptoPP::ClonableImpl<CryptoPP::SHA1, CryptoPP::AlgorithmImpl<CryptoPP::IteratedHash<unsigned int, CryptoPP::EnumToType<CryptoPP::ByteOrder, 1>, 64u, CryptoPP::HashTransformation>, CryptoPP::SHA1> >::Clone() const in amule[0x48df99]
[13] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f9f7ee103f6]
[14] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f9f7ee10564]
[15] wxEvtHandler::ProcessEvent(wxEvent&) in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f9f7ee10887]
[16] wxEvtHandler::ProcessPendingEvents() in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f9f7ee10360]
[17] wxAppConsole::ProcessPendingEvents() in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f9f7ed93899]
[18] wxAppBase::ProcessIdle() in /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0[0x7f9f7f52b539]
[19] ?? in /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0[0x7f9f7f4a5dae]
[20] g_main_context_dispatch in /lib/x86_64-linux-gnu/libglib-2.0.so.0[0x7f9f7bc0eddd]
[21] ?? in /lib/x86_64-linux-gnu/libglib-2.0.so.0[0x7f9f7bc0f1b8]
[22] g_main_loop_run in /lib/x86_64-linux-gnu/libglib-2.0.so.0[0x7f9f7bc0f4e2]
[23] gtk_main in /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0[0x7f9f7da0fbc7]
[24] wxEventLoop::Run() in /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0[0x7f9f7f4b9268]
[25] wxAppBase::MainLoop() in /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0[0x7f9f7f52b33c]
[26] wxEntry(int&, wchar_t**) in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f9f7edc24e5]
[27] ?? in amule[0x44f252]
[28] __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6[0x7f9f7df4ab45]
[29] ?? in amule[0x45b325]


- Issue History
Date Modified Username Field Change
2014-09-12 13:58 adri58 New Issue
2014-09-12 13:58 adri58 File Added: logfile
2014-09-12 14:00 adri58 File Added: amule.conf
2014-09-14 12:28 GonoszTopi Note Added: 0003638
2014-09-14 12:28 GonoszTopi Status new => feedback
2014-09-14 15:57 adri58 Note Added: 0003639
2014-09-14 15:57 adri58 Status feedback => new
2014-09-15 11:53 nsaspy Note Added: 0003640
2014-09-15 22:21 adri58 Note Added: 0003643
2014-09-17 16:28 adri58 Note Edited: 0003643 View Revisions


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker