Borland memory manager bugs???

[bNasty]

Hello,
I have a very strange crash in BCB. My app is allocating big number of small objects (using 'new'), but suddenly, it started crashing in Borlandmm.dll!
Surely, there is a plenty of memory, and, anyway, it shouldn't crash, but it does and I can't do anything about it!
Does anyone know of any reported bugs in Borland memory manager? If so, is there a way to fix it?

Thanks

 

[Totte]

Well, for one thing i wonder HOW MANY objects?
And what are the size of those small objects?
Remember that the program needs a far pointer to the memory located and if the allocated size is a long pointer you actually allocates twice the memory needed....
Does it crash during the allocating or are there unallocating involved before the crash?

Totte

 

[bNasty]

Essentialy, the size shouldn't matter, since app was crashing inside Borlandmm.dll! That's just unacceptable! Memory manager must allocate me one byte if I ask for!

But anyway, I got around the problem by overriding global new/delete operator and using LocalAlloc() inside it. It works just fine now, but this bug(?) in Borlandmm.dll is very disturbing...