On Wed, May 5, 2010 at 9:20 AM, James Carlson <[email protected]>wrote:
> > It's a leak of sorts. It's adding entries to an AVL tree endlessly. > > > ::umausers > 105584384 bytes for 1649756 allocations with data size 64: > libumem.so.1`umem_cache_alloc_debug+0x144 > libumem.so.1`umem_cache_alloc+0x19a > libumem.so.1`umem_alloc+0xcd > libumem.so.1`malloc+0x2a > libumem.so.1`calloc+0x4a > linkattr_set+0x74 > dlmgmt_readconf+0x8a > dlmgmt_handler+0xec > 32995120 bytes for 412439 allocations with data size 80: > libumem.so.1`umem_cache_alloc_debug+0x144 > libumem.so.1`umem_cache_alloc+0x19a > libumem.so.1`umem_alloc+0xcd > libumem.so.1`malloc+0x2a > libumem.so.1`calloc+0x4a > dlconf_create+0x1f > dlmgmt_readconf+0x5f > dlmgmt_handler+0xec > [...] > > dlmgmt_dlconf_avl::walk avl ! wc -l > 412440 > > The short answer would probably be "don't do that." These appear to be > due to clients reading the configuration over and over again. > > Thanks for the analysis. It doesn't seem related to the bug ID that I found. Should I open a new one in bugs.opensolaris.org ? -- Giovanni
_______________________________________________ networking-discuss mailing list [email protected]
