aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: various bugs  (Read 3912 times)

boutros

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 53
various bugs
« on: November 24, 2005, 10:04:40 AM »
I run my aMule (GTK1, full monolithic version) 24x7 on a virtual Xvnc session and of course I need it to be stable, both crash wise and memory wise. aMule 2.0.3 is great, reliable, and doesn't memory leak.

However!

There are a few things I would like to do.

1. Scrap Xvnc and run the daemonised version of amuled
2. Use a unicode version of amule
3. Use kadmelia

But!

1. Under amuled a particular file might stay red for days (no sources). Under the full amule it finds sources..... Is this a known issue and has it been fixed?

2. Unicode means to link with GTK2 and every time I've tried it, it memory leaks all over the place. Has this been fixed yet? Maybe this is an external problem in wxGTK, but if it is, is there a way round it?

3. Using kad means to switch to a CVS version of amule, which I did and it memory leaked very very very badly. I had to revert.

So..

There must be a way for me to achieve 1, 2 and 3. But I appreciate that running with CVS versions we will run into problems, and I know what a pain in the 4ss it is to memory profile a complex bit of code. Is there are particular recent CVS version out there with known good memory allocation behaviour?

Thanks folks
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: various bugs
« Reply #1 on: November 24, 2005, 10:09:21 AM »
1. not a know problem on my side

2. fixed since wxGTK-2.6.2, but wx-2.6.2 has a locale bug, so the best version atm would be wx-cvs

3. hmmm havent noticed this aswell....could this be due to point 2?
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685
Re: various bugs
« Reply #2 on: November 24, 2005, 12:36:06 PM »
To be able to use wxWidgets-2.6.2, you have to patch the sources according to this thread.
Logged
concordia cum veritate

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: various bugs
« Reply #3 on: November 24, 2005, 01:19:37 PM »
You can use 2.6.1 with current aMule CVS and have almost nothing regarding memleaks.
Logged

boutros

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 53
Re: various bugs
« Reply #4 on: December 02, 2005, 10:22:09 AM »
Quote
Originally posted by Kry
You can use 2.6.1 with current aMule CVS and have almost nothing regarding memleaks.

OK well I tried it. I am using amuled with Unicoded GTK2 wxGTK 2.6.2 with December the 1st's CVS snapshot of aMule.

Amuleweb is a lot nicer these days eh? :-)

It did memory leak a very tiny bit but not as bad as the previous times I've tried it. Startup memory usage is at 115MB, and 24 hours later is up at 156Mb, and still 24 hours later 216MB. However I can't test past this point in time because the client goes wrong :-

Kad turns itself off after 24 hours of runtime. Whereas before it said "Kad ok", it says "Kad off". It won't reactivate. The bootstrap button on amulegui does nothing.

Since I run Kad only, and turn ED2K off, that about killed the client off for me.

Note that if I run the monolithic client, Kad stays up. I also get these wierdnesses where a file will stay red for hours or unless I restart the client. I verify that these instances are not my mistake by seeing complete sources using the Razorback2 stats facility.

But the client's getting there, far superior to anything else on the Linux platform.
Logged

boutros

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 53
Re: various bugs
« Reply #5 on: December 06, 2005, 01:31:20 AM »
Well, kad gets disconnected and won't restart, and now I get amuled using all memory and all swap (1GB + 1GB impressive bug!) and being killed by the kernel.

No backtrace was possible

I've upgraded to the latest CVS version to see if these problems still exist.
Logged

Gerd78

  • Hero Member
  • *****
  • Karma: 9
  • Offline Offline
  • Posts: 681
Re: various bugs
« Reply #6 on: December 06, 2005, 01:46:49 AM »
Quote
Originally posted by boutros
Well, kad gets disconnected and won't restart, and now I get amuled using all memory and all swap (1GB + 1GB impressive bug!) and being killed by the kernel.
That's probably something else, not related to wx. I think it's this one:

http://forum.amule.org/thread.php?threadid=8280
Quote
Originally posted by Xaignar
By any chance, do you run software to synchronize your clock?

[...]

Yeah, currently aMule will fall over if the time gets changed into the past. Ken is currently working on fixing it, so it should hopefully work in tomorrows snapshot.
Logged

boutros

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 53
Re: various bugs
« Reply #7 on: December 06, 2005, 10:42:16 AM »
Code: [Select]
$ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*ntp0.linx.net   128.86.8.123     2 u  216 1024  377   35.032  -52.855   7.186
Indeed, you are correct, I think it was this. The currect CVS seems to be fixed in this respect.
Logged