10-25-2012
All memory allocated by a process is returned to the system when the process terminates.
A very small amount of memory will remain after the process terminates that indicates the status of the terminated process. That memory will be released when the process that started the terminated process either gathers the exit status of its dead child (by calling something like wait()) or terminates.
This User Gave Thanks to Don Cragun For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi!! Experts,
Any ideas how to check for the memory leaks in a process during performance testing?? I dont use purify.. Any way of finding it out using default S/W in HP UX-11
Can U gimme pointers to site having good scripts/tutorials on performance testing??
Thanx in Advance..
:) (3 Replies)
Discussion started by: jyotipg
3 Replies
2. 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
3. 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
4. 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
5. 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
6. 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
7. 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
8. 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
9. 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
10. 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
exit(2) System Calls Manual exit(2)
Name
_exit - terminate a process
Syntax
#include <stdlib.h>
void _exit(status)
int status;
Description
The function, terminates a calling process with the following consequences:
o All of the file descriptors open in the calling process are closed.
o If the parent process of the calling process is executing a it is notified of the calling process's termination and the low-order
eight bits of status are made available to it. For further information, see
o The parent process ID of all of the calling process's existing child processes and zombie processes are also set to 1. This means
that the initialization process inherits each of these processes as well. For further information, see
o Each attached shared memory segment is detached and the value of shm_nattach in the data structure associated with its shared memory
identifier is decremented by 1.
o For each semaphore for which the calling process has set a semadj value, (see ) that semadj value is added to the semval of the speci-
fied semaphore.
o If the process has a process, text, or data lock, an unlock is performed.
o An accounting record is written on the accounting file if the system's accounting routine is enabled. For more information, see
Calling directly circumvents all cleanup. Most C programs call the library routine which performs cleanup actions in the standard I/O
library before calling
Environment
POSIX, System V
The function differs from the System V as well as POSIX definition in that even if the calling process is a process group leader, the
SIGHUP signal is not sent to each process that has a process group ID equal to that of the calling process.
The function also differs in that the routine is declared as type int instead of type void.
See Also
fork(2), wait(2), exit(3), signal(3).
exit(2)