From: robin <robin@india•tejasnetworks.com>
To: Gerhard Jaeger <g.jaeger@sysgo•com>,
linuxppc-embedded@ozlabs•org, etux@embeddedtux•org
Subject: Memory leak problem
Date: Fri, 11 Feb 2005 11:59:04 +0530 [thread overview]
Message-ID: <200502111159.04265.robin@india.tejasnetworks.com> (raw)
In-Reply-To: <200502100840.38232.g.jaeger@sysgo.com>
Hi=20
Thanks for your help.=20
We found the memory leak in the syncppp module in linux.
1. Did somebody encounter any problems(leaks) with the=20
syncppp module in denx 2.4.20 kernel??=20
2. Are there any known issues with this module??
The scenario is we are ftp-ing continuosly between=20
two nodes using syncppp module. The leak is ocuring at=20
both the nodes.
Regards,
Robin
On Thursday 10 Feb 2005 1:10 pm, Gerhard Jaeger wrote:
> On Thursday 10 February 2005 07:07, robin wrote:
> > Hi
> > We have an application running on denx linux kernel 2.4.20.
> >
> > Apparently there is a memory leak that we are not able to find.
> > The application is giving out of memory error. Even if we restart
> > the application without rebooting the kernel, (killing all applicatio=
n
> > processes and restarting), it gives the same out of memory error.
> > Rebooting the kernel solves the problem.
> >
> > It seems that the memory leak is not at the application level
> > 'cos restarting the application doesnt solve the problem..
> >
> > 1. Any ideas where I should look for the leak??
>
> Check /proc/slabinfo and see if there are some "supicious" buffer,
> that only increase and never decrease. From the kind of buffer
> showing this behaviour you might find out where to dig...
> Check it before running the application and afterwards.
>
> > 2. Is there any known memory leak problems with the kernel??
>
> There are enough places, where a kernel could leak, but in general
> such leaks in the main part are detected really fast. Undiscovered
> leaks are often found in the drivers itself.
>
> What's your kernel config?
> Which HW are you using?
> What does this application?
>
> Ciao,
> Gerhard
--=20
And I hate redundancy, and having different functions for the same thing.
=09- Linus Torvalds on linux-kernel
next prev parent reply other threads:[~2005-02-11 6:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 17:13 Problems with Serial Port on IceCube Linas Petras
2005-02-04 19:21 ` Wolfgang Denk
2005-02-10 6:07 ` Memory leak problem robin
2005-02-10 7:40 ` Gerhard Jaeger
2005-02-10 9:46 ` robin
2005-02-11 6:29 ` robin [this message]
2005-02-11 10:53 ` Wolfgang Denk
2005-02-06 18:06 ` Problems with Serial Port on IceCube Sylvain Munaut
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=200502111159.04265.robin@india.tejasnetworks.com \
--to=robin@india$(echo .)tejasnetworks.com \
--cc=etux@embeddedtux$(echo .)org \
--cc=g.jaeger@sysgo$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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