aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: 1 2 3 [4]

Author Topic: Wake up from tray bar, full RAM usage and closing  (Read 19810 times)

myth

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 38
  • Offline Offline
  • Posts: 570
Re: Wake up from tray bar, full RAM usage and closing
« Reply #45 on: September 24, 2009, 10:45:14 PM »
Nope...and also with non-debug-build it crashes... :/

But I have a suspect: Maybe it happens only when I call back aMule from tray (or taskbar), when in the time it was minimized, the (Kad) IP changed...could this be?
Logged

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685
Re: Wake up from tray bar, full RAM usage and closing
« Reply #46 on: September 24, 2009, 10:54:03 PM »
There shouldn't be any relation of the two. ("shouldn't be" is not necessarily equal to "there isn't" - but I don't know how could a Kad IP change influence a GUI restore event)
Logged
concordia cum veritate

myth

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 38
  • Offline Offline
  • Posts: 570
Re: Wake up from tray bar, full RAM usage and closing
« Reply #47 on: September 25, 2009, 07:22:46 PM »
Quote
but I don't know how could a Kad IP change influence a GUI restore event

I also don't believe it ;)

Was my information good enought to find the bug?
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: Wake up from tray bar, full RAM usage and closing
« Reply #48 on: September 25, 2009, 08:18:04 PM »
I'm afraid not.  :(
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

myth

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 38
  • Offline Offline
  • Posts: 570
Re: Wake up from tray bar, full RAM usage and closing
« Reply #49 on: September 26, 2009, 01:04:36 PM »
Well...I'm running it again with valgrind. For now i can provide my ./configure and make output:

./configure

make

EDIT: Here also some line from the terminal:

http://pastebin.org/25919

Look at the last lines!
« Last Edit: September 26, 2009, 01:07:44 PM by myth »
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: Wake up from tray bar, full RAM usage and closing
« Reply #50 on: September 26, 2009, 01:23:29 PM »
You should run the massif heap profile, not the error checker.
And yeah, CryptoPP is buggy. We all know that.  :(
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

myth

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 38
  • Offline Offline
  • Posts: 570
Re: Wake up from tray bar, full RAM usage and closing
« Reply #51 on: September 29, 2009, 07:42:43 PM »
It crashed!

Here is the Massif Output file: RS (1,1 MiB)

I hope it helps!
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: Wake up from tray bar, full RAM usage and closing
« Reply #52 on: September 29, 2009, 11:17:41 PM »
Yes and no...  :-\
Code: [Select]
#-----------
snapshot=84
#-----------
time=9887090961847
mem_heap_B=244515253
mem_heap_extra_B=84623107
mem_stacks_B=0
heap_tree=peak
n7: 244515253 (heap allocation functions) malloc/new/new[], --alloc-fns, etc.
 n2: 136686880 0xBB1FCD8: _XSend (in /usr/lib/libX11.so.6.2.0)
  n2: 136686880 0xBB1FF1F: _XReply (in /usr/lib/libX11.so.6.2.0)
   n1: 136686880 0xBAFD244: XGetWindowProperty (in /usr/lib/libX11.so.6.2.0)
    n1: 136686880 0x8486730: (within /usr/lib/libgdk-x11-2.0.so.0.1600.1)
     n1: 136686880 0x8486AE5: (within /usr/lib/libgdk-x11-2.0.so.0.1600.1)
      n1: 136686880 0x8486F0C: (within /usr/lib/libgdk-x11-2.0.so.0.1600.1)
       n1: 136686880 0x9F51208: g_main_context_dispatch (in /usr/lib/libglib-2.0.so.0.2000.1)
        n1: 136686880 0x9F548DE: (within /usr/lib/libglib-2.0.so.0.2000.1)
         n1: 136686880 0x9F54DAB: g_main_loop_run (in /usr/lib/libglib-2.0.so.0.2000.1)
          n1: 136686880 0x7F6FBC5: gtk_main (in /usr/lib/libgtk-x11-2.0.so.0.1600.1)
           n2: 136686880 0x672AA26: wxEventLoop::Run() (in /usr/lib/libwx_gtk2u_core-2.8.so.0.6.0)
            n1: 136686880 0x67B08B9: wxAppBase::MainLoop() (in /usr/lib/libwx_gtk2u_core-2.8.so.0.6.0)
             n1: 136686880 0x6E2755B: wxEntry(int&, wchar_t**) (in /usr/lib/libwx_baseu-2.8.so.0.6.0)
              n0: 136686880 0x6A27C5: main (amule-gui.cpp:94)
            n0: 0 in 1 place, below massif's threshold (01.00%)
   n0: 0 in 5 places, all below massif's threshold (01.00%)
  n0: 0 in 2 places, all below massif's threshold (01.00%)
 n2: 50920296 0x6E47D76: wxStringBase::Alloc(unsigned long) (in /usr/lib/libwx_baseu-2.8.so.0.6.0)
  n2: 50843096 0x6E47F39: wxStringBase::ConcatSelf(unsigned long, wchar_t const*, unsigned long) (in /usr/lib/libwx_baseu-2.8.so.0.6.0)
   n2: 50687288 0x6E49A31: wxString::wxString(char const*, wxMBConv const&, unsigned long) (in /usr/lib/libwx_baseu-2.8.so.0.6.0)
    n2: 50673976 0x7FA758: CFileDataIO::ReadOnlyString(bool, unsigned short) const (SafeFile.cpp:254)
     n3: 43802176 0x7F88E7: CFileDataIO::ReadString(bool, unsigned char, bool) const (SafeFile.cpp:226)
      n2: 22940920 0x7F9773: CFileDataIO::ReadTag(bool) const (SafeFile.cpp:434)
       n1: 21646560 0x654012: Kademlia::CKademliaUDPListener::Process2PublishKeyRequest(unsigned char const*, unsigned int, unsigned int, unsigned short, Kademlia::CKadUDPKey const&) (KademliaUDPListener.cpp:1579)
        n1: 21646560 0x663629: Kademlia::CKademliaUDPListener::ProcessPacket(unsigned char const*, unsigned int, unsigned int, unsigned short, bool, Kademlia::CKadUDPKey const&) (KademliaUDPListener.cpp:352)
         n2: 21646560 0x624A47: Kademlia::CKademlia::ProcessPacket(unsigned char const*, unsigned int, unsigned int, unsigned short, bool, Kademlia::CKadUDPKey const&) (Kademlia.cpp:292)
This first block is expanding rapidly, probably until memory exhaustion. It's all in GDK/X, and probably triggered by your restoring it from the icon. But there is no aMule code directly involved, so I can't say where to put my finger on.  :(
Should we start debugging X now? Are there any updates available you haven't yet?
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

myth

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 38
  • Offline Offline
  • Posts: 570
Re: Wake up from tray bar, full RAM usage and closing
« Reply #53 on: September 30, 2009, 08:39:19 PM »
Shit :/

WxWidgets have to do something with it?

It seems they are installed correctly.

To be shure I'm just trying to download and install 2.9.0 version. (now I have 2.8.10)

EDIT: I won't change the wxwidgets right now...I don't feel like it now :P
« Last Edit: September 30, 2009, 08:54:43 PM by myth »
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: Wake up from tray bar, full RAM usage and closing
« Reply #54 on: October 01, 2009, 10:17:38 PM »
You might run into lots of new & interesting problems with 2.9 ...  :-\
I have no idea if it's wx, GTK or X11. I don't know how they work together. All I can say is that XGetWindowProperty allocates memory for its return value. So it's obviously called in an infinite loop until memory is exhausted. I'd guess it's a GTK problem. Of course the complex tray icon code might also be related in some way. Can you just disable the tray icon?
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

myth

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 38
  • Offline Offline
  • Posts: 570
Re: Wake up from tray bar, full RAM usage and closing
« Reply #55 on: October 02, 2009, 08:01:42 PM »
OK, I disabled tray icon right now ;)
Logged

myth

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 38
  • Offline Offline
  • Posts: 570
Re: Wake up from tray bar, full RAM usage and closing
« Reply #56 on: November 10, 2009, 09:49:11 PM »
Strange but nice thing: I installed Ubuntu Linux 9.10 (2.6.31-14-generic) amd64, and until now I didn't encounter the problem any more! :)
Logged

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685
Re: Wake up from tray bar, full RAM usage and closing
« Reply #57 on: November 10, 2009, 09:55:11 PM »
Hopefully it was just aMule triggering a bug in another library which has already been fixed. Though it would be interesting to know...
Logged
concordia cum veritate
Pages: 1 2 3 [4]
« previous next »