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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
