Important update released.

@ MBOS,

I could not replicate your scenario. However, I was able to get such a crash in another context/scenario (for me like a random scenario).
My scenario though was only replicable in the IDE and not on the executable.
I was able to find the cause for it and the explanation.

Due to the VTableHandle.bas update on 25-Feb-2018 the IOleInPlaceActiveObject switched from Subclassed to own lightweight VTable object.
The issue is that the lightweight VTable object relies on AddressOf functions and that these addresses could go "invalid" (addresses in .bas module changed) on unload.

The straight forward solution was now to restore the original IOleInPlaceActiveObject object in the DeActivateIPAO method. So it is safe in either case to unload.