For a project I created a little server using libsoup-3, and after using it for several days, I found that the browser began to get laggy and even crash. After doing a lot of research I found that the version bundled with Raspbian (3.2.2, the same available in Debian Bookworm, obviously) has a bug, and when the client closes a connection, the server doesn't closes the socket, thus leaving it in CLOSE_WAIT state forever (until the server is restarted, of course). The bug has been fixed in newer libsoup versions (both in 3.4 and the current upstream stable 3.6).
Since Debian testing has this fixed, I was wondering if I can just update the whole Raspbian to testing. Or should I just use pinning to update only the libsoup package?
(yes, I already sent a bug report to Debian and specified the commit with the patch, but I'm not sure when will they apply it, test it, upload...).
Since Debian testing has this fixed, I was wondering if I can just update the whole Raspbian to testing. Or should I just use pinning to update only the libsoup package?
(yes, I already sent a bug report to Debian and specified the commit with the patch, but I'm not sure when will they apply it, test it, upload...).
Statistics: Posted by rastersoft — Sat Dec 07, 2024 8:32 am — Replies 0 — Views 19
