|
MALLOC_MEMORY_HOLD and C++
|
07/31/2013 1:04 PM
post103799
|
MALLOC_MEMORY_HOLD and C++
If we use MALLOC_MEMORY_HOLD=1 programs heaps will go very fast, I mean within minutes they will have consume the
maximum process memory space. There is no memory leak, apparently it`s memory fragmentation other with
MALLOC_MEMORY_HOLD=0 the problem would show up.
So far I don`t understand why this is happening, in a nut shell we`ve taken existing C program, replace their malloc
with new or std::vector<>.
Has anyone got any idea what is going on or how I might fiddle with some MALLOC_* options to fix this. In the mean time
i will try to create a program to reproduces the problem.
|
|
|