mirror of
https://github.com/juce-framework/JUCE.git
synced 2026-01-10 23:44:24 +00:00
b060d5d947
Observed on Ubuntu Linux. Occasionally, the loop checking the condition_variable in the plugin scanner would spin indefinitely. The cause appears to be that handleMessageFromWorker could be called immediately after sendMessageToWorker, but before locking the mutex. If this happens, gotResponse will be false during every call to condvar.wait_for, and the loop will never exit. The rewritten version of the scanner always resets gotResult immediately after the condvar is woken successfully, so a call to handleMessageFromWorker or handleConnectionLost will always cause a subsequent call to condvar.wait_for to exit successfully. The Superprocess class has also been refactored and extracted to avoid a circular dependency between Superprocess and CustomPluginScanner. |
||
|---|---|---|
| .. | ||
| Builds | ||
| JuceLibraryCode | ||
| Source | ||
| AudioPluginHost.jucer | ||
| CMakeLists.txt | ||