Apparently, event names are GLOBAL so reusing the same name is VERY DUMB
This commit is contained in:
parent
6b6ca8fe60
commit
36fb572308
|
@ -238,7 +238,7 @@ namespace winrt::TerminalApp::implementation
|
|||
// ready to go. We won't need the event after this function, so the
|
||||
// unique_event will clean up our handle when we leave this scope. The
|
||||
// ContentProcess is responsible for cleaning up its own handle.
|
||||
wil::unique_event ev{ CreateEvent(nullptr, true, false, L"contentProcessStarted") };
|
||||
wil::unique_event ev{ CreateEvent(nullptr, true, false, nullptr/*L"contentProcessStarted"*/) };
|
||||
// Make sure to mark this handle as inheritable! Even with
|
||||
// bInheritHandles=true, this is only inherited when it's explicitly
|
||||
// allowed to be.
|
||||
|
|
|
@ -138,7 +138,7 @@ void TryRunAsContentProcess()
|
|||
HANDLE eventHandle{ INVALID_HANDLE_VALUE };
|
||||
if (checkIfContentProcess(contentProcessGuid, eventHandle))
|
||||
{
|
||||
g_canExitThread = wil::unique_event{ CreateEvent(nullptr, true, false, L"ContentProcessReady") };
|
||||
g_canExitThread = wil::unique_event{ CreateEvent(nullptr, true, false, nullptr/*L"ContentProcessReady"*/) };
|
||||
|
||||
doContentProcessThing(contentProcessGuid, eventHandle);
|
||||
|
||||
|
|
Loading…
Reference in a new issue