03-16-2006
delete does release all of the memory, except memory that you explicitly allocated with a separate malloc call, which is not very common in C++.
If you are seeing that the program's process seems to keep memory after a delete call, it's because of the os, not your code. The operation to get more memory is expensive, so the os usually holds onto memory until the process exits.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
This is on HP UNIX version 11. I have a shared memory segment that is marked for deallocation .... see below
m 521 0x00000000 D-rw-rw---- oracle dba
The D says it marked for deallocation. I tried to do the ipcrm -m 521. The message said it cannot find the segment. I assume... (1 Reply)
Discussion started by: joecbc
1 Replies
2. UNIX for Advanced & Expert Users
I am running HP-UX B.11.11.
I'm increasing a parameter for a database engine so that it uses more memory to buffer the disk drive (to speed up performance). I have over 5GB of memory not being used.
But when I try to start the DB with the increased buffer parameter I get told.
"Not... (1 Reply)
Discussion started by: cjcamaro
1 Replies
3. Programming
Hi, I try to marshal a unsigned int and a char * into a buffer, and then unmarshal them later to get them out. I need to put the char * in the front and unsigned int at the end of the buffer. However, my system always give me "BUS ERROR". I am using Sun Sparcs Sloris 2.10.
My code to marshal... (6 Replies)
Discussion started by: nj302
6 Replies
4. HP-UX
Refer from title:
How can i get memory used or anything that can show memory from sar file
example on solaris:-
we can use sar with option to show memory used at time that sar crontab run.
on HP-UX, it not has option to see memory used. But i think it may be have some parameter or some... (1 Reply)
Discussion started by: panithat
1 Replies
5. 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
6. Programming
Hi,
I'm trying to learn how to manage memory when I have to deal with lots of data.
Basically I'm indexing a huge file (5GB, but it can be bigger), by creating tables that
holds offset <-> startOfSomeData information. Currently I'm mapping the whole file at
once (yep!) but of course the... (1 Reply)
Discussion started by: emitrax
1 Replies
7. Solaris
Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies
8. UNIX for Advanced & Expert Users
I was running a program and it stopped and showed "Out of Memory!". at that time, the RAM used by this process is around 4G and the free memory size of the machine is around 30G. Does anybody know what maybe the reason? this program is written with Perl. the OS of the machine is Solaris U8. And I... (1 Reply)
Discussion started by: lilili07
1 Replies
9. Shell Programming and Scripting
Dear all,
I find a perl script that contains the following codes. Does anybody know the meaning of codes highlight.
.....
@field = parse_csv($file);
chomp(@field);
........
........
sub parse_csv {
my $text = shift;
my @new = ();
push( @new, $+ ) while $text =~ m{... (9 Replies)
Discussion started by: eldonlck
9 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
LEARN ABOUT DEBIAN
reallocf
MALLOC(3) BSD Library Functions Manual MALLOC(3)
NAME
reallocf -- general purpose memory allocation functions
LIBRARY
Utility functions from BSD systems (libbsd, -lbsd)
SYNOPSIS
#include <bsd/stdlib.h>
void *
reallocf(void *ptr, size_t size);
DESCRIPTION
The reallocf() function changes the size of the previously allocated memory referenced by ptr to size bytes. The contents of the memory are
unchanged up to the lesser of the new and old sizes. If the new size is larger, the contents of the newly allocated portion of the memory
are undefined. Upon success, the memory referenced by ptr is freed and a pointer to the newly allocated memory is returned. Note that
reallocf() may move the memory allocation, resulting in a different return value than ptr. If ptr is NULL, the reallocf() function behaves
identically to malloc() for the specified size. Upon failure, when the requested memory cannot be allocated, the passed pointer is freed to
ease the problems with traditional coding styles for reallocf() causing memory leaks in libraries.
RETURN VALUES
The reallocf() function returns a pointer, possibly identical to ptr, to the allocated memory if successful; otherwise a NULL pointer is
returned, and errno is set to ENOMEM if the error was the result of an allocation failure. The buffer is deallocated in this case.
SEE ALSO
brk(2), mmap(2), alloca(3), calloc(3), free(3), malloc(3), posix_memalign(3), realloc(3),
HISTORY
The reallocf() function first appeared in FreeBSD 3.0.
BSD
September 26, 2009 BSD