C#

Bob_Sun wrote:

BeginInvoke and EndInvoke should be called in pair,

Tehnoon wrote:

I have used BeginInvoke so many times in so many performance critical applications without using EndInvoke, it doesn't create a problem

Daniel Grunwald wrote:

delegate.BeginInvoke (creates new thread [from thread-pool]) without delegate.EndInvoke will cause a memory leak.

Tehnoon wrote:

Can you show the code in which you are invoking the thread which is creating the problem? Garbage collection will not be done unless the thread is finished with the execution. The only possibility that I am seeing here is that the system is not being able to provide all the requested resources by the program and hence the results are not coming out as expected. A look at the source code will give me a better idea of this.

public class Control
{
    private StateMachine myStateMachine = new StateMachine();

    public void EventProc1()
    {
        ....
        EventHandler eventHandler = new EventHandler(this.Thread1);
        eventHandler.BeginInvoke(this,null,null,null);
    }

    public void EventProc2()
    {
        ....
        EventHandler eventHandler = new EventHandler(this.Thread2);
        eventHandler.BeginInvoke(this,null,null,null);
    }

    protected void Thread1(object sender,EventArgs e)
    {
        LogMessage("Start of thread1");
        this.myStateMachine.Dispatch(1);
    }

    protected void Thread2(object sender,EventArgs e)
    {
        LogMessage("Start of thread2");
        this.myStateMachine.Dispatch(2);
    }
}

public class StateMachine
{
    public void Dispatch(event id)
    {
        switch(event id)
        {
            case 1:
                ....
                break;
            case 2:
                ....
                break;
            ...
            default:
                break;
        }
    }
}