[omniORB] High virtual memory shown for omniNames

[Duncan Grisby]

On Fri, 2015-06-26 at 06:35 +0000, Agarwal, Shelendra wrote:

> Recently we have noticed that omniNames shows very high virtual
> memory. The output of below command shows around 9GB of vss. Though
> there is no memory leak as over a period of time we don’t see memory
> to be growing but we are unable to understand why there is such high
> memory shown for this simple process.

How many entries are you storing in omniNames?  As you say, it is a very
simple process. It stores all the names in memory, because the
expectation is that the CORBA naming service contains just a small
number of entry-point services. If you are storing vast numbers of
entries, that would explain why it is big.

The other possible use of memory is in iterator objects. If your clients
receive iterators, they are responsible for destroying them.

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --