C# Discussion Boards - CodeProject

Re: Memory leaks while calling functions from another assembly.

8-Sep-10 1:56

Hi all,

In our application, we need to call functions from external assembly. Below is what we have already done?

1 Please note that user can create his own assemblies and can call any static public functions in those assemblies from our application.

2 Once the user has created his assembly, he let our application know which function in that assembly is to be called.

3 We load user specified assembly in a separate application domain.

4 We determine if the function that user wants to execute, actually exists in that assembly. (For this we use reflection to get complete information of the assembly).

5 Then we create parameters that are to be passed to the function in external assembly. For preparing parameters we are using a class Arg derived from interface MarshalByRefObject as below:

internal abstract class Arg : MarshalByRefObject
{
...
}

So Arg's object will represent parameters to be passed.

6 Now the problem comes. More the parameter we pass to a function in external assembly, more the memory leaks are there. If we call a function several times, memory leaks grows proportionally (even when that separate app-domain is unloaded).

7 So the reason of these memory leaks is that parameters (represented by Arg class derived from MarshalByRefObject) are not being collected by Garbage Collector (even when called explicitly).

8 Any comment on how can we free objects of Arg (created for passing parameters)? Or is there something that we should take extreme care about while doing stuff like this?

Regards
Aseem

Luc Pattyn8-Sep-10 2:27

Re: Memory leaks while calling functions from another assembly.

8-Sep-10 2:27

when objects are no longer required yet fail to get collected, the most common cause is you still are referencing them somehow. Maybe you have a collection of Arg instances somewhere, which is growing all the time? A simple Clear() could fix that. Remember, a static class is loaded and initialized on its first use and never relinquished.

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

Aseem Sharma8-Sep-10 2:48

Re: Memory leaks while calling functions from another assembly.

8-Sep-10 2:48

The objects that we are creating are purely local to a function. And we don't have even a single global/static variable. So the reason is something else. I guess it has something to do with either Application-Domain or MarshalByRefObject. Something we should take care about them which we are not doing.

Luc Pattyn8-Sep-10 2:55

Re: Memory leaks while calling functions from another assembly.

8-Sep-10 2:55

People may need to see the relevant code, in order to help you out.

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

Aseem Sharma8-Sep-10 3:41

Re: Memory leaks while calling functions from another assembly.

8-Sep-10 3:41

I am sorry, I am not authorized to share the code. Also I cannot produce similar sample of code. Its too big and complex to understand. And I myself have just 1 month of experience in .Net.

This problem is very specific. Someone if know the things to be taken care about Application-Domain and MarshalByRefObject while calling functions from external assembly?

As objects derived from MarshalByRefObject are not getting collected by Garbage Collector, there could be some special way of freeing them from memory.

Pete O'Hanlon8-Sep-10 4:41

Pete O'Hanlon

8-Sep-10 4:41

Have a read of this[^] article and pay particular attention to the lease management.

I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be

Forgive your enemies - it messes with their heads

My blog | My articles | MoXAML PowerToys | Onyx

Re: Memory leaks while calling functions from another assembly.

Luc Pattyn9-Sep-10 16:07

Re: Memory leaks while calling functions from another assembly.

9-Sep-10 16:07

Seems I was unaware of the potential problems with MarshalByRefObject.
Here[^] is another article you may want to read.

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

David Knechtges8-Sep-10 3:42

David Knechtges

8-Sep-10 3:42

I would see stuff like this when I was using mixed (managed C++) code. What I found was that the references to the called DLLs were not being released unless I unloaded them by hand.

So, what you might try is loading the DLLs dynamically in your C# app, then unloading them and setting their references to null when finished using them. Each time a DLL function is called, you might then reload the DLL, but this might help you get rid of your memory leak.

Re: Memory leaks while calling functions from another assembly.

Aseem Sharma8-Sep-10 3:59

Re: Memory leaks while calling functions from another assembly.

8-Sep-10 3:59

Once an assembly (a .Net dll) is loaded, it cannot be unloaded and so it will remain in application's address space until process's life time. To avoid this we should load an assembly in a separate application domain. An application domain can be unloaded whenever we want and while it unloads, it also unload all assemblies loaded inside it. So problem can not be resolved as you said. But yes, as you said we have mixed code of Unmanaged C++, Managed C++ and C#. Could this mix of code have any implication?

Jason J. Chase12-Sep-10 20:31

Jason J. Chase

12-Sep-10 20:31

To be 100% sure what the problem is, crack out windbg with the SOS extension for .Net. You can use ADPlus to take a memory dump of the .Net process in question, and then load the dump file into windbg.

The SOS debugger extension is used for debugging .Net memory dumps. Using !dumpheap -stat will show you all instances of objects on the heap. Given an instance handle, using !gcroot <handle> will tell you which thread is keeping the instance alive. Using !clrstack for that thread will show you the stack for that thread, pin pointing the exact code.

These commands are only the tip of the iceberg though, check out Tess Fernandez's blog at http://blogs.msdn.com/b/tess/[^] for help on using windbg for memory leak debugging in .Net.

Thread.Join() and GUI

Keith Vitali8-Sep-10 0:39

Keith Vitali

8-Sep-10 0:39

Hi everyone,

I have a question about how to handle Thread.Join() and the cases where the thread is updating using Invoke.

The problem is my background thread calls back into a method periodically that uses Invoke() to update some GUI elements. Now, when I call Join() on my background thread (in response to the user cancelling the job and the application waiting for the thread to finish), the whole application hangs as the subsequent Invoke() calls never return because Join() is blocking the caller thread (i.e. my main thread).

Does anyone know how I can get around this? Thread.Sleep() is no use either as I do want the main thread to be responsive and at least handle these UI events. I was under the impression that the message pump was supposed to be active when using Thread.Join()

Cheers,
Pankaj

Luc Pattyn8-Sep-10 0:59

8-Sep-10 0:59

Why would you need Thread.Join() in your main thread? As I told you recently, the main thread should never take long and should never block. Thread.Join() is OK when one background thread needs to wait on another background thread, you should not use it in the main thrad.

If your main thread needs to know some background activity is finished, use another mechanism; however most of the time, you should not be interested in when exactly the background activity finishes, all you need to do is set a flag that tells it you are no longer interested, which allows it to exit early and tells it not to produce anything anymore (yes, your code now needs to test that flag on every action you don't want to go on).

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

Kubajzz8-Sep-10 1:03

Kubajzz

8-Sep-10 1:03

I have 2 suggestions:

1. Do not use the Thread class unless you have to, because it adds a lot of complexity (could BackgroundWorker do the job?)

2. I would never use Thread.Join() unless I really had to... What if you just set a flag to notify the background thread about the cancellation and wait for the thread to complete without calling Join()?

Fayu8-Sep-10 4:09

Fayu

8-Sep-10 4:09

Just because you call a join does not mean that the function that you are running is terminated. When calling join, the caller (in your case the background process) will block indefinetly as long as the thread has not terminated. If the thread is completed, then the join method will end immediately. To fix your problem, ensure that you are exiting the function that is running in the background thread when the user 'cancels' the request.