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.
The program above exits without freeing the memory.
In this case will the 1 gb of heap memory be returned to system on above process termination or has the heap memory permanently leaked and will be available only on system reboot?
I mean if say we start some another process or say the same process again then will they be able to get the 1 gb if heap again?
Last edited by rupeshkp728; 10-25-2012 at 12:49 PM..
Reason: code syntax
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)
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)
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)
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)
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)
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)
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)
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
chi::driver::memory
CHI::Driver::Memory(3pm) User Contributed Perl Documentation CHI::Driver::Memory(3pm)NAME
CHI::Driver::Memory - In-process memory based cache
VERSION
version 0.54
SYNOPSIS
use CHI;
my $hash = {};
my $cache = CHI->new( driver => 'Memory', datastore => $hash );
my $cache = CHI->new( driver => 'Memory', global => 1 );
DESCRIPTION
This cache driver stores data on a per-process basis. This is the fastest of the cache implementations, but data can not be shared between
processes. Data will remain in the cache until cleared, expired, or the process dies.
To maintain the same semantics as other caches, references to data structures are deep-copied on set and get. Thus, modifications to the
original data structure will not affect the data structure stored in the cache, and vica versa. See CHI::Driver::RawMemory for a faster
memory cache that sacrifices this behavior.
CONSTRUCTOR OPTIONS
When using this driver, the following options can be passed to CHI->new() in addition to the CHI. One of datastore or global must be
specified, or else a warning (possibly an error eventually) will be thrown.
datastore [HASHREF]
A reference to a hash to be used for storage. Within the hash, each namespace is used as a key to a second-level hash. This hash may
be passed to multiple CHI::Driver::Memory constructors.
global [BOOL]
Use a standard global datastore. Multiple caches created with this flag will see the same data. Before 0.21, this was the default
behavior; now it must be specified explicitly (to avoid accidentally sharing the same datastore in unrelated code).
DISCARD POLICY
For CHI/SIZE AWARENESS caches, this driver implements an 'LRU' policy, which discards the least recently used items first. This is the
default policy.
SEE ALSO
CHI::Driver::RawMemory, CHI
AUTHOR
Jonathan Swartz <swartz@pobox.com>
COPYRIGHT AND LICENSE
This software is copyright (c) 2011 by Jonathan Swartz.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
perl v5.14.2 2012-05-30 CHI::Driver::Memory(3pm)