Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Kry]

I think it's time to talk to the Powers That Be, Stu.

But wait for me to do so, don't do it yourself for now.

[EloiBosc]

Great, you're under way. The "trust value" can be a smart solution: Weeks ago I manually blocked these addresses and since then amuled is stable.

In my July 26 post I quoted some brisk memory rise due to a spontaneous "Stop/Start Kad". This is caused by a detection of no-kad-traffic on the udpport. The port is not receiving and it is turned off/on to unblock. On my amuled this happens 1 or 2 times per day.

I checked the income packets looking for something (high udp traffic, malformed packets, ...) but apparently all was normal when the udpport was blocked. I'd like to know what part is responsible (os, wxWidgets, amule, ...) and some solution, since the code is protected about it somebody may know. I didn't find references, only some on wxWidgets (I put last version: no changes).

[gav616]

I'm convinced '979*' have fixed the massive mem leak.......?

..couple of days up-time ATM, and its still under 90mb (same number onqueue,  downloads,  KAD-only, build flags)
It looks 'better' to me anyway.

[gav616]

forget my last post, today mule is taking nearly 400mb with 1 download and 400 on queue. (9871)

[EloiBosc]

If you got big key_index.dat, cause of big memory usage, and while waiting for a solution based on "trust value" try to filter (iptables or other) the nets:

sudo iptables -A INPUT -s 129.47.136.0/24 -j DROP
sudo iptables -A INPUT -s 129.47.160.0/24 -j DROP
sudo iptables -A INPUT -s 129.47.161.0/24 -j DROP
sudo iptables -A INPUT -s 129.47.147.0/24 -j DROP

[p.r.]

I have a similar problem with amuled 2.2.6.

If KAD is disabled amuled VmSize is about 12-13MB.

IF KAD is enabled memory usage begins to slowly and continuously grow -
amuled starts with VmSize 18MB and 10 hours later VmSize reaches 30MB,
size of key_index.dat grows from 1MB to 2M.
But in my case Moblock doesn't detect any Whittaker IPs, although I know for sure these ip ranges are in my ipfilter.p2p

When I was running amuled 2.2.3 with KAD enabled VmSize never went over 20MB.

[Stu Redman]

Sounds perfectly normal to me. Information gets posted slowly and so memory usage grows slowly. Does it still increase further after 24 hours?

When I was running amuled 2.2.3 with KAD enabled VmSize never went over 20MB.

How long ago was that? And same conditions?  You know, just a different KAD-ID might get you to a "hotter" spot in the network with more data to handle.

[p.r.]

Sounds perfectly normal to me. Information gets posted slowly and so memory usage grows slowly. Does it still increase further after 24 hours?
...

Yes,  perhaps it's normal, but I have little RAM - 32MB.
I don't run amuled for 24h.

...

When I was running amuled 2.2.3 with KAD enabled VmSize never went over 20MB.

How long ago was that? And same conditions?
...

It was two months ago,  conditions didn't changed except  Shared Files that increased a little in number.

...  You know, just a different KAD-ID might get you to a "hotter" spot in the network with more data to handle.

Yes, perhaps that is true.
Today amuled 2.2.6  (with enabled KAD) starts with VmSize 14MB, and 6 hours later VmSize reaches 20MB.  Size of key_index.dat grows from 70kB to 380kb.

[Stu Redman]

You will be having trouble running KAD with 32MB. That's a fact.

Try the SVN version with the mmap configure option - it has a bunch of optimizations for low memory platforms.

[p.r.]

Stu Redman
aMuled SVN with  mmap enabled  don't reduce or limit VmSize.

[Stu Redman]

Well, at least it should cut some peaks, like at hashing.

[gav616]

This is definitely fixed for me with 'mmap'.

wxgtk 2.8.10

Code: [Select]

  --with-gtk=2 --enable-gui --enable-graphics_ctx --enable-unicode \
  --disable-all-features --without-odbc --without-expat --without-libmspack --without-sdl
amule-svn

Code: [Select]

--disable-monolithic \
--enable-amule-daemon \
--disable-amulecmd \
--disable-webserver \
--enable-amule-gui \
--disable-cas \
--disable-wxcas \
--disable-ed2k \
--disable-alc \
--disable-alcc \
--disable-upnp \
--disable-xas \
--enable-geoip \
--enable-mmap \
--disable-nls \
--disable-debug
obviously this for a minimal remote gui setup only, but still, its fixed.

[Stu Redman]

Ha, just checked my "productive" environment. Windows had increased the swap file. aMule was at 140MB memory, 60001 entries in the keyword index (13.8MB saved), 46939 from 129.47.136.* 
That's 129.47.136.215     US     United States     CA     California     Simi Valley     93063     34.3021     -118.7208     Whittaker Corporation     Whittaker Corporation 

Kry, any news? I'm starting to think a hard coded Kad firewall of that IP range would not be such a bad idea.

[Kry]

Look into a way to solve the problem, not workaround it. Check what can we see that would help detect it behaviouraly and feel free to talk about it in less public places.

In case whoever is doing that is reading this: Poisoning a distribution network is not the way to fight anything, no matter what your reasons are. You are intentionally disrupting a networking service intentionally, and that's very morally, if not legally, wrong. I'm all for fighting for law compliance with the respective's country law, but you're disrupting a content delivery service that hosts plenty of legal files, and most of them outside your country.