You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happened when I have installed Lingoes 2.9.1(http://www.lingoes.net/) and run it in the back.
When the bundle starts, it will load a dll from Lingoes.(C:\Users\Administrator\AppData\Local\Lingoes\Translator\lingoes-us\OpenText32.dll)
It looks like OpenText32.dll will call CoInitializeEx using a different thread mode before bundle's EngineRun().
When using the debug version of burn.exe, the generated bundle will crash because "ExitOnFailure(hr, "Failed to initialize COM.");" try to use the LogStringWork() before LogInitialize().
When using the release version of burn.exe, it won't crash.
but the CoInitializeEx is failed and I assume the COM is not initialized with COINIT_MULTITHREADED.
Will this affect the bundle's behavior?
I searched CoInitializeEx on msdn and it says,
Because there is no way to control the order in which in-process servers are loaded or unloaded, do not call CoInitialize, CoInitializeEx, or CoUninitialize from the DllMain function.
There is certainly something Lingoes is doing wrong, but maybe we should still make sure the bundle will behavior good under such environment .
Originally opened by uni
The text was updated successfully, but these errors were encountered:
CoInitializeEx returns 0x80010106 - Cannot change thread mode after it is set.
This happened when I have installed Lingoes 2.9.1(http://www.lingoes.net/) and run it in the back.
When the bundle starts, it will load a dll from Lingoes.(C:\Users\Administrator\AppData\Local\Lingoes\Translator\lingoes-us\OpenText32.dll)
It looks like OpenText32.dll will call CoInitializeEx using a different thread mode before bundle's EngineRun().
When using the debug version of burn.exe, the generated bundle will crash because "ExitOnFailure(hr, "Failed to initialize COM.");" try to use the LogStringWork() before LogInitialize().
When using the release version of burn.exe, it won't crash.
but the CoInitializeEx is failed and I assume the COM is not initialized with COINIT_MULTITHREADED.
Will this affect the bundle's behavior?
I searched CoInitializeEx on msdn and it says,
Because there is no way to control the order in which in-process servers are loaded or unloaded, do not call CoInitialize, CoInitializeEx, or CoUninitialize from the DllMain function.
There is certainly something Lingoes is doing wrong, but maybe we should still make sure the bundle will behavior good under such environment .
The text was updated successfully, but these errors were encountered: