Using Delphi and C++Builder Results in Problems With the Borland Memory Manager

Article #21181: Using Delphi and C++Builder Results in Problems With the Borland Memory Manager

Question:

Why do I have problems using C++Builder 4.0 and Delphi 4.0 with the memory manager?

Answer:

What happens is when the C++Builder part is loaded the borland memory manager is loaded and rips the memory manager out from underneath the Delphi side. To fix this add the unit

ShareMem

as the first unit to the Delphi project file (dpr). This is a problem with Delphi since it will never load the borland memory manager. This has been fixed in C++Builder 5.0 and Delphi 5.0. So as long as you are using packages and you have the borland memory manager DLL in the search path you will be fine.

Last Modified: 12-APR-00