Bug#1109685: libsoup-3.0-0: deadlock with gstreamer1.0-plugins-good 1.26.2-1

[Nick Steel]

Brilliant, thank you very much for sorting this out.

Cheers,
Nick

On Thu, 24 Jul 2025, at 12:20 PM, Simon McVittie wrote:
> On Thu, 24 Jul 2025 at 10:13:08 +0100, Simon McVittie wrote:
> >On Tue, 22 Jul 2025 at 13:32:34 +0100, Nick Steel wrote:
> >>most of Mopidy's value comes from extensions (mostly distributed via PyPI
> >>etc) and it's these that are exposed to the bug, some are consequently
> >>rendered unusable
> >
> >How can this deadlock be reproduced on a Debian system, preferably 
> >with software from Debian only, or with third-party code if necessary?
> >
> >GModule uses a recursive lock, so the most obvious reproducers like
> >
> >    g_module_open_full ("/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstsoup.so", 0, error);
> >
> >do not deadlock: any reproducer would need to be multithreaded.
> 
> I was able to reproduce this with the attached artificial test-case. 
> (Good result: it runs for 10 seconds of high CPU load and then exits 
> gracefully. Bad result: it continues to run indefinitely, with CPU use 
> dropping to zero when it becomes deadlocked.)
> 
> I confirm that the upstream change makes the test-case work as it 
> should.
> 
>      smcv
> 
> 
> *Attachments:*
>  • 1109685.c
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20250725/7f151f19/attachment-0001.htm>