--- In [email protected], "entropyreduction"
<alancampbelllists+ya...@...> wrote:
>
> If so, whatever the problem is, it only affects scripts using certain COM
> objects.
>
> In any case, couldn't hurt, so I rewrote my code, substituting
> CoWaitForMultipleHandles for WaitForSingleObject. No difference.
>
> Added message loop. No difference.
It's been a long time since the last time I used com.dll. IIRC, it sometimes
worked, sometimes didn't. Why don't you upload it to somewhere for the users
who always experienced the crash to test.
> Removed extra thread, ran all calls to COM api on the main pp thread.
> That made problem with Com.Unload in this script go away:
>
> Local num = "12345678"
> Local vbs = Com.Create_Object("ScriptControl")
> vbs.Language = "VBScript"
> Local formatted = vbs.Eval("FormatNumber(&(num),0)")
> vbs = Com.Release(vbs)
> Com.Unload
>
> But then create_object failed in e.g. comPluginDemoScriptWord.powerpro,
> comPluginDemoScriptWordDotSyntax.powerpro.
>
It looks like having a problem with a local/out-of-process COM server. I'm not
sure if it's due to PP. I'd like to ask this first, to be sure, do you use the
same code for CreateObject (via CoCreateInstance, right?) for both ones? What
values of CLSCTX did you use, CLSCTX_ALL or CLSCTX_SERVER?
