[opensource-dev] Mesh viewers and tcmalloc issues

[Mike Chase]

On 10/02/2011 12:45 PM, Henri Beauchamp wrote:
> On Sun, 02 Oct 2011 10:20:58 -0400, Mike Chase wrote:
>
>> One more note.  I have 16gb of memory on this system so the large heap
>> really isnt a problem per-se.
> It is, because you will not be able to get more than 3Gb of virtual
> memory per process, and when this virtual space gets fragmented (which
> *does* happen during "long" sessions with tcmalloc and its default
> release rate), your viewer will crash trying to allocate the next
> unfragmented space that won't fit its currently allocated but
> fragmented pool.
Ok, point taken. Even though I'm on a 64bit system the executable is 32 
bit so yes, 3gb will be the max memory. And I do see it creep in that 
direction.  It would be nice to have a 64bit native executable. But that 
path has been tread before.  I don't expect to see that any time soon.

So what allocator is Firestorm using?  It sits around 1.6gb for me where 
the dev viewer keeps growing.

Mike