Invoke handle error on close despite multiple sanity checks

Question

I'm using this small utility function:

public static void Invoke(Control control, Action method)
{
    if (control.InvokeRequired)
    {
        if (control.IsDisposed || !control.IsHandleCreated || !control.Created)
            return;
        control.Invoke(method);
    }
    else
        method();
}

Despite all of those sanity checks, when I close my application, a stray invoke always produces this error:

Invoke or BeginInvoke cannot be called on a control until the window handle has been created.

This, despite there clearly being a check to see if the handle is created... What else can I do?

score 2 · Accepted Answer · edited May 23 '17 at 12:04

2

Read through this thread which delves into Invoke'ing. The problem you're experiencing is almost certainly down to a control disappearing between the if(...) return; and the Invoke doing its thing.

edited May 23 '17 at 12:04

Community

1
1

answered May 17 '11 at 23:15

Will A

24,392
5
48
60

1

That was indeed helpful. When I replaced all usage of Invoke with BackgroundWorker (whose progress report event had to be somewhat abused to achieve the desired behaviour) it runs without complaint. – Reinderien May 24 '11 at 06:16

Invoke handle error on close despite multiple sanity checks

1 Answers1