10-26-2012
Quote:
Originally Posted by
alister
In the open source world, that hasn't been true for about 10 years. Linux (glibc), OpenBSD, NetBSD, and FreeBSD all return memory to the system under certain circumstances (such as free()ing a massive chunk).
This is contrary to what I have read...since the freed memory return to the OS pool only when the process exits. I maybe wrong but this seems to contradict what I read in this
book...besides frequent garbage collection by the OS is going to make the kernel sweat. In fact whatever I understood about runtime memory allocation from that book is exactly what Corona688 posted.
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
PAE(4) BSD/i386 Kernel Interfaces Manual PAE(4)
NAME
PAE -- Physical Address Extensions
SYNOPSIS
options PAE
DESCRIPTION
The PAE option provides support for the physical address extensions capability of the Intel Pentium Pro and above CPUs, and allows for up to
64 gigabytes of memory to be used in systems capable of supporting it. With the PAE option, memory above 4 gigabytes is simply added to the
general page pool. The system makes no distinction between memory above or below 4 gigabytes, and no specific facility is provided for a
process or the kernel to access more memory than they would otherwise be able to access, through a sliding window or otherwise.
SEE ALSO
smp(4), tuning(7), config(8), bus_dma(9)
HISTORY
The PAE option first appeared in FreeBSD 4.9 and FreeBSD 5.1.
AUTHORS
Jake Burkholder <jake@FreeBSD.org>
BUGS
Since KLD modules are not compiled with the same options headers that the kernel is compiled with, they must not be loaded into a kernel com-
piled with the PAE option.
Many devices or their device drivers are not capable of direct memory access to physical addresses above 4 gigabytes. In order to make use
of direct memory access IO in a system with more than 4 gigabytes of memory when the PAE option is used, these drivers must use a facility
for remapping or substituting physical memory which is not accessible to the device. One such facility is provided by the busdma interface.
Device drivers which do not account for such devices will not work reliably in a system with more than 4 gigabytes of memory when the PAE
option is used, and may cause data corruption. The PAE kernel configuration file includes the PAE option, and explicitly excludes all device
drivers which are known to not work or have not been tested in a system with the PAE option and more than 4 gigabytes of memory.
Many parameters which determine how memory is used in the kernel are based on the amount of physical memory. The formulas used to determine
the values of these parameters for specific memory configurations may not take into account the fact there may be more than 4 gigabytes of
memory, and may not scale well to these memory configurations. In particular, it may be necessary to increase the amount of virtual address
space available to the kernel, or to reduce the amount of a specific resource that is heavily used, in order to avoid running out of virtual
address space. The KVA_PAGES option may be used to increase the kernel virtual address space, and the kern.maxvnodes sysctl(8) may be used
to decrease the number of vnodes allowed, an example of a resource that the kernel is likely to overallocate in large memory configurations.
For optimal performance and stability it may be necessary to consult the tuning(7) manual page, and make adjustments to the parameters docu-
mented there.
BSD
April 8, 2003 BSD