wasted heap space

Discussion created by lpcware Employee on Jun 15, 2016
Latest reply on Jun 15, 2016 by lpcware
Content originally posted in LPCWare by charchar on Wed Mar 25 16:39:02 MST 2015
I'm playing with heap overflow checking mechanism by defining the function __check_heap_overflow.  This function gets called every time the heap grows past a 4K boundary.  I'm guessing because the heap advances 4K at a time.... Is there a way to tweak this value?  It results in up to 4K of memory being unallocatable (worst case) when the heap reaches its limit.