10-17-2002
ps -elf will show you the memory usage of processes on your system. You can run ps -elf every so often and compare the size of the processes between runs. If you see one getting larger, it is using more memory. If it continues to use more and more memory or stops doing any actual work and does not free up memory, you may have a leak. I say 'may' because some code will keep the pool of memory allocated to it and use it when it starts processing again.
10 More Discussions You Might Find Interesting
1. HP-UX
Hi folks,
We are using following listed configurations for a particular application.
HP-UX 11i
Sun Java 2 SDK Standard Edition 1.4.1 (version shipped with WebLogic 8)
Oracle 9i Release 2 (Oracle 9.2.0)
BEA WebLogic Server 8.1 SP3
It seems a memory leak when we use above configurations.... (1 Reply)
Discussion started by: gimhan90
1 Replies
2. Programming
hi, i am a c++ programmer working on linux(redhat linux8.0) environment, i need to find out the memory leaks, so far i didn't used any tools, so what are the tools are available, and whic one is good to use. plz provide with a small example. (1 Reply)
Discussion started by: sarwan
1 Replies
3. UNIX for Advanced & Expert Users
Hi Unix lovers,
I am facing a strange problem about memory leak. One component of our product show memory leak at customer's end but not in development environment. The memory used by the exe goes on increasing at customer end but not in dev.
customer has same m/c(HP unix 11i) , the same... (1 Reply)
Discussion started by: shriashishpatil
1 Replies
4. Shell Programming and Scripting
Hi all,
Has anyone out there a shell script to detect memory leaks on unix machines?
And if so what way did they go about it .? (5 Replies)
Discussion started by: nano2
5 Replies
5. UNIX and Linux Applications
Hello all
Is there good free ware tools to check software memory leaks ?
Some thing like purify
on unix platforms sun/hp/linux
Thanks (3 Replies)
Discussion started by: umen
3 Replies
6. Solaris
Hi,
Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:-
1. Total Physical Memory in the system(total RAM).
2. Available Physical Memory(i.e. RAM Usage)
3. Total (Logical) Memory in the system
4. Available (Logical) Memory.
I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies
7. AIX
Hi all,
I have written a small code just to invoke main and return immediately. When built with libpthread on AIX box, valgrind throws lots of memory leak errors. But when built without libpthread, no issues at all.
Here is the sample run for your look. Any idea where I might be going wrong?... (3 Replies)
Discussion started by: visionofarun
3 Replies
8. Emergency UNIX and Linux Support
Hello!
I've been struggling for not few hours with memory leaks on this
machine. I'm running linux 2.6.32-5-686, and the problem is as follows:
Some months ago, I have compiled kernel 2.6.33-2-686 without any issues
in this same machine. This week I have tried compiling GNUzilla Icecat
and... (23 Replies)
Discussion started by: teresaejunior
23 Replies
9. Solaris
Hi Experts,
Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing.
Why memory utilization on solaris always looks high?
I have statement about memory on solaris, is this true:
Memory in solaris is used for... (4 Replies)
Discussion started by: edydsuranta
4 Replies
10. Programming
Suppose I have a main() function with only one malloc statement allocating say some 1 gb memory. Also say my system has 1 gb of ram.
main()
{
malloc(1gb)
return(0)
}
The program above exits without freeing the memory.
In this case will the 1 gb of heap memory be returned... (9 Replies)
Discussion started by: rupeshkp728
9 Replies
LEARN ABOUT HPUX
serialize
serialize(2) System Calls Manual serialize(2)
NAME
serialize() - force target process to run serially with other processes
SYNOPSIS
DESCRIPTION
The system call is used to force the target process referenced by the pid value passed in to run serially with other processes also marked
for serialization. If the value of pid is zero, then the currently running process is marked for serialization. Once a process has been
marked by the process stays marked until process completion, unless is reissued on the serialized process with timeshare set to 1. If
timeshare is set to 1, the process specified in pid will be returned to normal timeshare scheduling algorithms.
This call is used to improve process throughput since process throughput usually increases for large processes when they are executed seri-
ally instead of allowing each program to run for only a short period of time. By running large processes one at a time, the system makes
more efficient use of the CPU as well as system memory, since each process does not end up constantly faulting in its working set, to only
have the pages stolen when another process starts running. As long as there is enough memory in the system, processes marked by behave no
differently from other processes in the system. However, once memory becomes tight, processes marked by are run one at a time with the
highest priority processes being run first. Each process runs for a finite interval of time before another serialized process is allowed
to run.
RETURN VALUE
returns zero upon successful completion, or nonzero if the system call failed.
ERRORS
If fails, it sets (see errno(2)) to the following value:
The pid passed in does not exist.
WARNINGS
The user has no way of forcing an execution order on serialized processes.
AUTHOR
was developed by HP.
SEE ALSO
serialize(1), privileges(5).
serialize(2)