Pipewire: ensure destruction on app thread
pipewire's stream classes contain socket notifier objects which needs to
be destroyed on the thread that runs their event loop.
The stateChanged handler is running on a pipewire thread, so we should
defer the release of the refcount to the app thread.
Fixes: QTBUG-149181
Pick-to: 6.12 6.11
Change-Id: Ia40f1ca2a4caeaed59ba14d0c287ad91659bf152
Reviewed-by: Artem Dyomin <artem.dyomin@qt.io>
| commit | a9ce561568914d88651278241e263e410363aeab |
| parent | b15f91894dde1b378a11c5738f87c595774f9a73 |
| author | Tim Blechmann <tim.blechmann@qt.io> |
| committer | Tim Blechmann <tim.blechmann@qt.io> |
| commit time | Tue, 18 Aug 2026 08:19:01 +0000 |