forked from bartvdbraak/blender
00133ba8f0
Our new guarded allocator implementation has much smaller memory block size overhead and doesn't have any locks now. So in order to make fuller track of what's happening in blender and avoid confusion why certain circumstances reports much less memory than others we'll now switch to guarded allocator. This was actually one of the biggest reasons of the confusion in the recent memory usage investigation. There's still some overhead is happening due to non-freeing nature of arena allocator but the things are not nearly as bad as they looked before: memory overhead is measured in tens of megabytes, not hundreds as it looked before. Plus with some smarter allocation policy we can almost eliminate this overhead. |
||
|---|---|---|
| .. | ||
| blender | ||
| blenderplayer | ||
| creator | ||
| gameengine | ||
| icons | ||
| CMakeLists.txt | ||
| SConscript | ||