Guys, Thank you all for the input. A new fix is at http://codereview.lindenlab.com/6723148/ . Please review it and/or test it. All comments/suggestions/complaints are welcome and much appreciated.
The reasons why we introduced this memory pool management scheme are because 1) we want to make the memory allocation/deallocation process more controllable. You might know that there are flaws in our code, third-parties code and graphics drivers which causes memory leaking or absurd memory allocations. Those flaws are normally very hard to catch. We want to extend this memory pool management to intercept and monitor all memory activities in the future. and 2) as some of you already pointed out, we ask for regular 4MB memory chunks from the heap to minimize memory address fragmentation. This is an on-going project. So if you have something you want me to know, please email me at b...@lindenlab.com. Thanks a lot, Bao On Tue, Sep 6, 2011 at 6:33 PM, Dave Booth <d...@meadowlakearts.com> wrote: > Gotta give kudos to Bao on this one.. > > After Grumpity assigned it, 1 minute from status "Acknowledged" to "Fix > Pending" - If you can zero in on it that fast, Bao, you are really in > tune with your code :) > > Looking forward to seeing your fix hit the trunk :) > _______________________________________________ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/OpenSource-Dev > Please read the policies before posting to keep unmoderated posting > privileges >
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
