Fix thread safety issue with VST2 plugin groups

While a VST2 plugin is being initialized in a plugin group, all host
callbacks would go over that new plugin instance's sockets. This would
cause a race condition if the host processes audio while loading
plugins. This issue has been there since the introduction of plugin
groups, but it's only noticeable in Bitwig Studio, and only when using
over thirty instances of the same plugin in a plugin group.
This commit is contained in:
Robbert van der Helm
2021-05-30 02:06:52 +02:00
parent b3d5a39001
commit 27c96135cb
2 changed files with 35 additions and 10 deletions
+4
View File
@@ -62,6 +62,10 @@ Versioning](https://semver.org/spec/v2.0.0.html).
### Fixed
- Fixed a longstanding thread safety issue when hosting multiple instances of a
VST2 plugin in a plugin group. This could cause plugins to crash or freeze
when initializing a new instance of a VST2 plugin in a plugin group while
another instance of the same plugin is processing audio.
- Fixed yabridge's Wine processes inheriting file descriptors in some
situations. This could cause **Ardour** and **Mixbus** to hang when trying to
reopen it after a crash. The watchdog timer added in yabridge 3.2.0 also