From: Avi Kivity <avi@argo.co.il>
To: Raj <inguva@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/pid/maps keeps growing
Date: Wed, 08 Feb 2006 12:48:03 +0200 [thread overview]
Message-ID: <43E9CC63.6070106@argo.co.il> (raw)
In-Reply-To: <b2fa632f0602080024r61bf1dbfr8bff6ae6a1860562@mail.gmail.com>
Raj wrote:
>I have been load testing a server running on RHEL 3.0 (2.4.21). I see that the
>/proc/pid/maps keeps growing.
>
>If the server is leaking memory, then i expected, the heap address to
>change rather than
>creating a new segment. As the server is a threaded app, i tried
>ld_preloading my own
>library to catch all pthread_create calls, but could catch only 4. So
>even threading doesnt
>seem to be an issue.
>
>so i am wondering now. I know the server is leaking memory. But i dont
>know where to look
> at.
>
>Can someone pls help me in letting me know, in which cases can a
>/proc/pid/maps file keep on increasing ?
>
>The server is running on IBM hardware, with 4GB ram. The maps file
>currently has 2200
>lines just like the ones pasted below.
>
>
>
malloc() and friends can use mmap() to allocate memory, usually for
larger allocations. looks like you have a leak.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2006-02-08 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 8:24 /proc/pid/maps keeps growing Raj
2006-02-08 10:48 ` Avi Kivity [this message]
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=43E9CC63.6070106@argo.co.il \
--to=avi@argo.co.il \
--cc=inguva@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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