vanja/yabridge
1
0
Fork 0
mirror of https://github.com/robbert-vdh/yabridge.git synced 2026-05-09 20:29:10 +02:00
Code Issues Packages Projects Releases Wiki Activity

Allow the group host to terminate cleanly

Browse Source 
...before terminating it forcefully. Not sure why this
`TerminateProcess()` was here instead of in `group-host.cpp` in the
first place. This way we don't have to duplicate any destructor
behaviour.
This commit is contained in:
Robbert van der Helm
2021-10-16 02:00:39 +02:00
parent 1b662c07a7
commit e3f0926aef
1 changed files with 2 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/wine-host/bridges/group.cpp
+2 -9
View File
@@ -334,15 +334,8 @@ void GroupBridge::maybe_schedule_shutdown(
logger.log( logger.log(
"All plugins have exited, shutting down the group process"); "All plugins have exited, shutting down the group process");
// main_context.stop(); // The whole process will exit in `group-host.cpp` because of this
// FIXME: See the comment in `individual-host.cpp`. Because of that main_context.stop();
// we also need to manually clean up the socket endpoint.
// ...was there a reason why we can't do this terminate at
// the end of `group-host.cpp`? I don't think there is. Then
// we don't need to duplicate this nasty destructor
// behaviour.
fs::remove(group_socket_endpoint.path());
TerminateProcess(GetCurrentProcess(), 0);
} }
}); });
} }