public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Axel Neumann <axel@open-mesh.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Memory leak
Date: Sun, 6 Jan 2008 15:03:08 +0100	[thread overview]
Message-ID: <200801061503.09053.axel@open-mesh.net> (raw)
In-Reply-To: <20080105214740.n00x2uza0coowssk@webmail.ddmesh.de>

Hi,

On Samstag 05 Januar 2008, Freifunk Dresden wrote:
> Hi,
>
> I have checked the problem a little more. Beside the "top" command on
> debian can show the same as the "top" does on WRTs. If you press 'H' the
> threads are also shown. Perhaps the implementation of the "top" or "ps"
> show the threads too.
>
> There are four batmand threads running. After a while one thread is
> terminated for about 100 seconds (25 x 4 seconds) and a new thread is
> created after
> this time. At this time the memory needs is increased. It seams that
> at each thread-kill-restart 16 Kbytes are wasted. The virtual assinged
> memory increases
> and also the %-Value used.

Does it really increase endlessly with each new thread ? 
If its the GW-client thread then you can enforce the termination and 
recreation on-the-fly with batmand -c -r0 (to destroy the tunnel) and 
-c -r3 (to create the tunnel)

>
> Below you will see the values (memory and pid) delivered by "top" for one
> incrementation.
> Hope it gives you a hint.
> Why is the thread killed and created? There is no client conntected to any
> router. rdate is restarted periodically and the laptop is telling that it
> has an internet connection (configured through batmand arguments, which is
> wanted).
> Note that the laptop does not have a connection to internet. It just
> pretends it has one.

there is a blackhole detection in the default two-way-tunnel. This can cause 
the client to disconnect from the unresponsive (-blackhole-) GW and put the 
GW on a blacklist for some time. It should all be reported on debug-level 3.
If no other GW is available, the GW-client node will reconnect to the GW after 
a while (might be 100 sec).
If you have a dummy GW, either use --no-unresp-gw-check or 
use --one-way-tunnel 3 at the client and the GW side 


/axel

>
>
> MEM: 1180   8%
> PIDS:1 -> 893 -> 894 -> 895
>                       -> 2673
>
> Pid 2673 terminates
> MEM: 1180   8%
> ....
> 100 seconds
> ....
> MEM: 1180   8%
> Pid 3751 is created
> MEM: 1196   9%
> 1 -> 893 -> 894 -> 895
>                  -> 3751
> MEM: 1196   9%
>
>
> Bye
>   Stephan
>
>
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n



  reply	other threads:[~2008-01-06 14:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04  9:57 [B.A.T.M.A.N.] Memory leak Freifunk Dresden
2008-01-04 20:24 ` Axel Neumann
2008-01-05 20:47   ` Freifunk Dresden
2008-01-06 14:03     ` Axel Neumann [this message]
2008-01-06 15:52       ` Freifunk Dresden
2008-01-07  9:45         ` Axel Neumann
2008-01-07 12:56           ` Freifunk Dresden
2008-01-07 16:48             ` [B.A.T.M.A.N.] one-way / two-way tunnel (was: Memory leak) Axel Neumann
2008-01-07 20:52               ` Freifunk Dresden
2008-01-10  8:25               ` Freifunk Dresden
2008-01-17 13:04   ` [B.A.T.M.A.N.] Memory leak Freifunk Dresden
2008-01-20 11:13     ` Axel Neumann
2008-01-26 21:04       ` Freifunk Dresden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200801061503.09053.axel@open-mesh.net \
    --to=axel@open-mesh.net \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox