mfcm.cpp causing memory leaks

Question

0.00/5 (No votes)

See more:

I have been getting a problem with a memory leak, and using the method of debugging the source of the problem was stated as in mfcm.cpp at line 29. The code sets up the load of the mfcm80DLL Dynamic Link Library via:

new CDynLinkLibrary(mfcm80DLL);

however there does not seem to be an associated FreeLibrary in the Code.

I am using this library to use the System namespace for various bits of data that I require.
How do I get round the memory leak problem, when the potential source is the mfc code?

Posted 12-Jun-12 12:37pm

psychokeith

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Aescleal · Answer 1 · 2012-06-12T13:25:00

This[^] looks like an explanation of the problem. Apparently if you use DLLs linked with different versions of the MFC DLL and is harmless.

A couple of things to consider... Not all memory leaks are worth tracking down. Compilers for example often use a slash and burn approach to dynamic memory - they allocate it and never bother releasing it. The real problem in C++ is not necessarily the memory leaking it's that the destructor doesn't get called.

And whatever you do, in your code never write new T; without immediately assigning the result to a smart pointer of some sort. Then you'll never leak memory and all your destructors will be called.