[prev in list] [next in list] [prev in thread] [next in thread] 

List:       omniorb-list
Subject:    Re: [omniORB] High virtual memory shown for omniNames
From:       Duncan Grisby <duncan () grisby ! org>
Date:       2015-06-26 16:03:33
Message-ID: 1435334613.16733.2.camel () home3 ! grisby ! org
[Download RAW message or body]

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

> Total number of entries are less than 100.
> 
> Also memory is not increasing, the value of 9g is shown at the start of
> the process itself, i.e. within few minutes of starting of omniNames.
> Non destroying of iterators by client would have resulted in gradual
> memory increase, right?

Yes, unless you have an initial client that spectacularly leaks enormous
numbers of iterators and then goes away for good, you would expect a
leak to cause a gradual increase.

Can you look at the process memory map and see what's so big?  You
didn't say what platform you're using, but for example on Linux you can
look at /proc/<pid>/smaps to get details of all the mapped memory
regions.

Cheers,

Duncan.

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



_______________________________________________
omniORB-list mailing list
omniORB-list@omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic