🚀 go-pugleaf

> Might be interesting to add
>
> GlobalFree( GlobalAlloc( GMEM_FIXED, 0x2000 ) );
> to your tests.

I saw no point in doing it, since GlobalAlloc works like HeapAlloc for 
process default heap. I ran it just to double check it and the results are 
exactly like HeapAlloc on process default heap. They all go through 
ntdll.RtlAllocateHeap.

> (Allocates 81,920,000 bytes)
> char*array[10000];
> void*memory[10000/16];
> for( int i=0; i<10000/16; ++i )
> { memory[i] = GlobalAlloc( GMEM_FIXED,16*0x2000);
> for( int j=0; j<16; ++j )
> array[i*16+j] = (char*)memory[i];
> };

> As i understand it, this is what malloc does, only bigger and more
> complicated.

As I understand memory manager would allocate chunk first and then malloc 
would get some pointer from it IF required amount is small enough to be 
allocated within commited pages. If we request more than commited, than 
malloc will call VirtualAlloc to commit more ( that takes long enough, 
longer than pure VirtualAlloc) . That means (note to self), that C RTL heap 
does not rely on Win32 heaps and goes for low level virtual function. It 
appears to me that initially C RTL memory manager allocates about 1MB. 
Thanks, by the way, your reply provoked me to check allocation of large 
amounts of memory.

Now, can we get rid of C RTL memory manager altogether, meaning no linking 
of cmt3260?

Azazello.