> On Jan 30, 2026, at 6:58 AM, Matthew Ruffell <[email protected]> > wrote: > > Hi Philip, > > I have reproduced the issue, and yes, the jammy package does indeed leak > memory. > > I have filed a LP bug to track the issue here: > > https://bugs.launchpad.net/ubuntu/+source/python-sysv-ipc/+bug/2139394 > > You can have a look at the debdiff I made to fix the bug here: > > https://launchpadlibrarian.net/845360510/lp2139394_jammy.debdiff
Great, thanks for the patch, and for letting me know about it! Cheers Philip > > On Mon, 12 Jan 2026 at 13:49, Philip Semanchuk <[email protected]> wrote: >> >> >> >>> On Jan 11, 2026, at 5:25 PM, Matthew Ruffell >>> <[email protected]> wrote: >>> >>> So, resolute, which is the current development release, will likely get >>> 1.2.0, >>> while the rest will remain as they are. >>> >>> For 1.0.0, focal is currently in ESM, and is unlikely to be fixed, but jammy >>> is still supported. If you are concerned about the memory leak, and if the >>> memory leak has actual real world impact to real users, then we can cherry >>> pick >>> the fix for the memory leak and fix it in jammy. >>> >>> In which case let me know a reproducer and I can make a bug in Launchpad, >>> and >>> we can sort that out. >> >> Hi Matthew, thanks for all the info! >> >> I don't have a great sense of how to assess the severity of the bug. The >> memory leak occurs on most writes to shared memory, so it's relatively easy >> to trigger, and the leak is the size of the data written, so it could add up >> quickly. That said, it's relatively easy for a Python user to pull a newer, >> non-buggy version of sysv_ipc from PyPI. I don't know how typical Ubuntu >> users feel about pulling packages from PyPI as opposed to official Ubuntu >> repositories. >> >> If you feel it's worth the effort to get a fix into jammy, the issue and a >> short script demonstrating the problem are here -- >> https://github.com/osvenskan/sysv_ipc/issues/7 >> >> Here's the (brief) commit that fixed the bug -- >> https://github.com/osvenskan/sysv_ipc/commit/03a4cb02af525369838369a857d0eb857eaf39ae >> >> This additional commit might be necessary if the compiler gives you grief. >> (Apparently it gave me grief because I included it in the same pull request >> as the leak fix.) >> https://github.com/osvenskan/sysv_ipc/commit/1a81cc7a44acd12331908bfa86cd405c3b89bc52 >> >> Cheers >> Philip >> >> >>> >>> On Sun, 11 Jan 2026 at 10:47, Philip Semanchuk <[email protected]> wrote: >>>> >>>> Hi, >>>> Apologies if this isn’t the right place for this message. I’m the author >>>> and maintainer of sysv_ipc (https://github.com/osvenskan/sysv_ipc/) which >>>> appears in Ubuntu as the package python3-sysv-ipc. I noticed that the >>>> Ubuntu version is using 1.0.0, which is not ideal because it contains a >>>> memory leak that was fixed in v1.0.1. >>>> >>>> I’ve just released version 1.2.0 which brought the project up to modern >>>> Python standards. Maybe that will make it easier for you to (re)package? >>>> >>>> Please contact me if I can help get a more current version into Ubuntu’s >>>> package repositories. >>>> >>>> Thanks >>>> Philip >>>> -- >>>> Ubuntu-devel-discuss mailing list >>>> [email protected] >>>> Modify settings or unsubscribe at: >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss >> -- Ubuntu-devel-discuss mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
