Clear Variant in DispatchComMethod.invoke before returning

[tonyroberts]

The returned Variant can contain an IDispatch/IUnknown, and leaving that to be cleared by the GC sometime later can cause issues if that doesn't happen on the correct thread.

Unlike COM wrapper objects, the Variant's finalizer doesn't schedule the actual clearing on the COM thread. Instead clearing just happens whenever the object is finalized, which can be on the wrong thread.

The invoke method is already running on the correct COM thread and so the safest fix is to simply clear the variant before returning.

Fixeskohsuke#91

[tonyroberts]

The returned Variant can contain an IDispatch/IUnknown, and leaving that to be cleared by the GC sometime later can cause issues if that doesn't happen on the correct thread.

Unlike COM wrapper objects, the Variant's finalizer doesn't schedule the actual clearing on the COM thread. Instead clearing just happens whenever the object is finalized, which can be on the wrong thread.

The invoke method is already running on the correct COM thread and so the safest fix is to simply clear the variant before returning.

Fixeskohsuke#91

[tonyroberts]

The returned Variant can contain an IDispatch/IUnknown, and leaving that to be cleared by the GC sometime later can cause issues if that doesn't happen on the correct thread.

Unlike COM wrapper objects, the Variant's finalizer doesn't schedule the actual clearing on the COM thread. Instead clearing just happens whenever the object is finalized, which can be on the wrong thread.

The invoke method is already running on the correct COM thread and so the safest fix is to simply clear the variant before returning.

Fixeskohsuke#91

[tonyroberts]

The returned Variant can contain an IDispatch/IUnknown, and leaving that to be cleared by the GC sometime later can cause issues if that doesn't happen on the correct thread.

Unlike COM wrapper objects, the Variant's finalizer doesn't schedule the actual clearing on the COM thread. Instead clearing just happens whenever the object is finalized, which can be on the wrong thread.

The invoke method is already running on the correct COM thread and so the safest fix is to simply clear the variant before returning.

Fixeskohsuke#91

[tonyroberts]

The returned Variant can contain an IDispatch/IUnknown, and leaving that to be cleared by the GC sometime later can cause issues if that doesn't happen on the correct thread.

Unlike COM wrapper objects, the Variant's finalizer doesn't schedule the actual clearing on the COM thread. Instead clearing just happens whenever the object is finalized, which can be on the wrong thread.

The invoke method is already running on the correct COM thread and so the safest fix is to simply clear the variant before returning.

Fixeskohsuke#91

[tonyroberts]

The returned Variant can contain an IDispatch/IUnknown, and leaving that to be cleared by the GC sometime later can cause issues if that doesn't happen on the correct thread.

Unlike COM wrapper objects, the Variant's finalizer doesn't schedule the actual clearing on the COM thread. Instead clearing just happens whenever the object is finalized, which can be on the wrong thread.

The invoke method is already running on the correct COM thread and so the safest fix is to simply clear the variant before returning.

Fixeskohsuke#91

[tonyroberts]

The returned Variant can contain an IDispatch/IUnknown, and leaving that to be cleared by the GC sometime later can cause issues if that doesn't happen on the correct thread.

Unlike COM wrapper objects, the Variant's finalizer doesn't schedule the actual clearing on the COM thread. Instead clearing just happens whenever the object is finalized, which can be on the wrong thread.

The invoke method is already running on the correct COM thread and so the safest fix is to simply clear the variant before returning.

Fixeskohsuke#91

[tonyroberts]

The returned Variant can contain an IDispatch/IUnknown, and leaving that to be cleared by the GC sometime later can cause issues if that doesn't happen on the correct thread.

Unlike COM wrapper objects, the Variant's finalizer doesn't schedule the actual clearing on the COM thread. Instead clearing just happens whenever the object is finalized, which can be on the wrong thread.

The invoke method is already running on the correct COM thread and so the safest fix is to simply clear the variant before returning.

Fixeskohsuke#91