CODEWITHSUNDEEP
c++builderteechartc++builder-6fastmm
AndyB
AndyB

Reputation: 362

FastMM reports 'Another third party memory manager has been installed' in BCB 6.0 & TeeChart 7.07

I've recently joined a new company with a suite of legacy apps written in C++ Builder 6 and am investigating some memory issues. To do this I'm using the latest Fast MM from GitHub and got it working ok with a simple BCB project.

In the actual projects, Fast MM says it can't start because 'Another third party memory manager has been installed'. After investigating this, it seems to be because of Teechart V7, which is used extensively in the projects.

If I add a Teechart control to my simple app I get the above message. We have the Teechart source code but I can't find anything in it that looks like a custom memory manager and am wondering if I can recompile it to use Fast MM. But, being a C++ Builder dev with very humble Delphi skills, I'm unsure if this is the right approach or why TeeChart causes Fast MM to think another memory manager is operating...

Any hints would be appreciated...

Andy

Upvotes: 0

Views: 252

Answers (1)

AndyB
AndyB

Reputation: 362

Teechart Pro V7 makes direct calls to the memory manager and building our app with runtime packages meant that TeeChart.bpl's dependency on the the Borland memory manager caused the problem. The simplest fix is to not include any Teechart package in the build with runtime packages list (assuming the linker can cope with the increased .EXE size) and/or use the third party ULink linker (ftp://ftp.styx.cabel.net/pub/UniLink/) which seems to cope with any size of deliverable.

Another option is to add FastMM to Teechart's projects (assuming you have the sources) and rebuild...

Upvotes: 0

Related Questions