Does dynamically allocating memory in a dll and attempting to release it outside the dll amount to memory leak?

Question

0.00/5 (No votes)

See more:

C++

Does dynamically allocating memory in a c-style dll and attempting to release it outside the dll amount to memory leak?

Posted 12-May-14 6:30am

Gbenbam

Add a Solution

4 solutions

Solution 4

Yes. Memory leak will happen.
Because allocating memory in c-style will depend on the crt-heap, and the crt-heap is a global variable value that initialized at the beginning of module initialization.
So, if you allocate memory in A module, but free it in B module, it won't find the correct handle of heap, and memory leak happens.

Posted 12-May-14 15:28pm

Heng Xiangzhong

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)

Mehdi Gholam · Accepted Answer · 2014-05-12T07:32:00

Solution 1

A memory leak is when you loose track of allocating and releasing memory, so if you keep track of your allocations then you won't have a leak.

Posted 12-May-14 7:32am

Mehdi Gholam

chandanadhikari · Accepted Answer · 2014-05-12T09:38:00

hi,
The basic rule of thumb is 'whoever allocated the memory, should free it too' . Its a helpful guideline which helps avoid trouble. Simply put, if memory was already allocated outside the dll and its handle is passed as input to the dll, then whichever entity did this memroy allocation,initially, should free it . And if the memory allocation was done ,say by a function inside the dll, then it is better to free it from within the dll itself. Anyways more googling should be helpful here.
Please take a look at this question[^]

Andreas Gieriet · Accepted Answer · 2014-05-12T09:50:00

Solution 3

No. It does not matter in which library the allocating code is located. I.e. while running the program, the memory model is independent of the way the code is linked.

On the other hand, for best practice, see the other solutions to your question.

Cheers
Andi

Posted 12-May-14 9:50am

Andreas Gieriet