Fix hanging processes for good #69

This commit is contained in:
Robbert van der Helm
2020-12-11 12:40:50 +01:00
parent 2615da51da
commit c306048988
3 changed files with 15 additions and 6 deletions
+2 -2
View File
@@ -33,8 +33,8 @@ Versioning](https://semver.org/spec/v2.0.0.html).
- Fixed an issue where in certain situations Wine processes were left running
after the host got forcefully terminated before it got a chance to tell the
plugin to shut down. This could happen when using Kontakt in Bitwig, as Bitwig
sets a limit on the amount of time a plugin may take to shut down when closing
Bitwig.
sets a limit on the amount of time a plugin may take to close when closing
Bitwig, and Kontakt can take a while to shut down.
- Fixed a potential crash or freeze when removing a lot of plugins from a plugin
group at exactly the same time.
+4 -1
View File
@@ -148,7 +148,10 @@ void GroupBridge::handle_plugin_dispatch(size_t plugin_id) {
if (active_plugins.size() == 0) {
logger.log(
"All plugins have exited, shutting down the group process");
main_context.stop();
// main_context.stop();
// FIXME: See the comment in `individual-host.cpp` #69
TerminateProcess(GetCurrentProcess(), 0);
}
});
}
+9 -3
View File
@@ -85,9 +85,15 @@ main(int argc, char* argv[]) {
Win32Thread dispatch_handler([&]() {
bridge->handle_dispatch();
// When the sockets get closed, this application should terminate
// gracefully
main_context.stop();
// // When the sockets get closed, this application should
// // terminate gracefully
// main_context.stop();
// FIXME: So some of the background threads spawned by the plugin may
// get stuck if the host got terminated abruptly. After an entire
// day of debugging I still have no idea whether this is a bug in
// yabridge, Wine, or those plugins, but just killing off this
// process and all of its threads 'fixes' the issue. #69
TerminateProcess(GetCurrentProcess(), 0);
});
// Handle Win32 messages and X11 events on a timer, just like in