mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-11-01 22:58:50 -04:00
9a6f8d31dc
When we are the owners of the loop lock and we are not in the loop thread itself, release all locks so that the loop can start processing our invoke items and we get a chance to make progress. After that re-acquire the locks. This can happen when you change some of the core loop_locked() calls to blocking _invoke functions that are called with the loop locked. We have all core blocking invoke functions removed now so this is not actually going to be used but just in case an application tries to blocking invoke while locking the loop, this will now at least do something else than deadlock. |
||
|---|---|---|
| .. | ||
| examples | ||
| include | ||
| include-private/spa-private | ||
| lib | ||
| plugins | ||
| tests | ||
| tools | ||
| meson.build | ||