forked from bartvdbraak/blender
c8d2bc7890
We don't have vectors re-allocation happening multiple times from inside a loop anymore, so we can safely switch to a memory guarded allocator for vectors and keep track on the memory usage at various stages of rendering. Additionally, when building from inside Blender repository, Cycles will use Blender's guarded allocator, so actual memory usage will be displayed in the Space Info header. There are couple of tricky aspects of the patch: - TaskScheduler::exit() now explicitly frees memory used by `threads`. This is needed because `threads` is a static member which destructor isn't getting called on Blender's exit which caused memory leak print to happen. This shouldn't give any measurable speed issues, reallocation of that vector is only one of fewzillion other allocations happening during synchronization. - Use regular guarded malloc (not aligned one). No idea why it was made to be aligned in the first place. Perhaps some corner case tests or so. Vector was never expected to be aligned anyway. Let's see if we'll have actual bugs with this. Reviewers: dingto, lukasstockner97, juicyfruit, brecht Reviewed By: brecht Differential Revision: https://developer.blender.org/D1774 |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| device_cpu.cpp | ||
| device_cuda.cpp | ||
| device_intern.h | ||
| device_memory.h | ||
| device_multi.cpp | ||
| device_network.cpp | ||
| device_network.h | ||
| device_opencl.cpp | ||
| device_task.cpp | ||
| device_task.h | ||
| device.cpp | ||
| device.h | ||