2006-02-08 08:24:08

by Raj

Subject: /proc/pid/maps keeps growing

Hi,

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.

Please Cc on the replies. Thanks very much for the help.


----------------Last 30 lines of the maps file----------------------
be400000-be5fe000 rw-p 0002e000 00:00 0
be5fe000-be600000 ---p 00000000 00:00 0
be600000-be6fa000 rw-p 000df000 00:00 0
be6fa000-be700000 ---p 00000000 00:00 0
be700000-bebfd000 rw-p 00095000 00:00 0
bebfd000-bec00000 ---p 00000000 00:00 0
bec00000-becff000 rw-p 00595000 00:00 0
becff000-bed00000 ---p 00100000 00:00 0
bed00000-beefe000 rw-p 00101000 00:00 0
beefe000-bef00000 ---p 00000000 00:00 0
bef00000-beffe000 rw-p 00002000 00:00 0
beffe000-bf000000 ---p 00000000 00:00 0
bf000000-bf0ff000 rw-p 00002000 00:00 0
bf0ff000-bf100000 ---p 00000000 00:00 0
bf100000-bf1fd000 rw-p 00001000 00:00 0
bf1fd000-bf200000 ---p 00000000 00:00 0
bf200000-bf4f9000 rw-p 00003000 00:00 0
bf4f9000-bf500000 ---p 00000000 00:00 0
bf500000-bf6ff000 rw-p 00007000 00:00 0
bf6ff000-bf700000 ---p 00000000 00:00 0
bf700000-bf7fc000 rw-p 000c7000 00:00 0
------------------------End--------------------------------

2006-02-08 10:48:11

by Avi Kivity

Subject: Re: /proc/pid/maps keeps growing

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