I also wanted to add that the arena freelist is an
optional feature. NSS uses the arena freelist, which
is what makes it difficult to track down some memory
leaks. I am fine with changing NSS to not use the
arena freelist.
Wan-Teh
___
dev-tech-crypto
Jean-Marc Desperrier wrote:
Quite an interesting description.
But I have a problem with it, this doesn't say *why* this is faster than
malloc/free. I'm listing three possible explanations below.
I think it's important to understand it has to be explained by one those
three reasons, and not jus
Nelson B wrote:
[...]. When NSS attempt to allocate more memory from an
arena pool, the PLArenaPool code attempts to use an arena from its
free list, and only gets a new arena from the heap if there are no
arenas in the free list that are large enough to satisfy the request.
[...]
To solve that
Matthew Gertner wrote:
> Hi,
>
> We're using NSS inside a Windows app for encrypted communication.
> Everything works fine, but we're experiencing a large number of memory
> leaks. Tracking down the cause led me to the following stacktrace (among
> many others):
>
> nspr4.dll!PR_Malloc(unsigned i
4 matches
Mail list logo
