Re: proc leaking
- To: Samuel Thibault <samuel.thibault@gnu.org>
- Cc: bug-hurd <bug-hurd@gnu.org>, debian-hurd@lists.debian.org
- Subject: Re: proc leaking
- From: Richard Braun <rbraun@sceen.net>
- Date: Fri, 1 Dec 2023 14:17:18 +0100
- Message-id: <[🔎] ZWnc3uU5ROvRPAZt@dalaran>
- In-reply-to: <20231126193230.d5iwvdwhx2h3s7yr@begin>
- References: <20231026224206.xzfca7l2s3bc7hjy@begin> <20231027064819.4gj3yr6uleanpszp@begin> <20231029222722.oj43wv5p7aanf7ka@begin> <20231030173503.xmu4k46y4h75nspu@begin> <20231031034043.eofz4saxo2vmsj4d@begin> <20231101005040.mevifhloadracihz@begin> <20231101121417.a6qqlxzmfjvxdfzx@begin> <20231101143500.52do53m4ul4cpx3r@begin> <20231101150657.7gnxrjmkv2jnsix4@begin> <20231126193230.d5iwvdwhx2h3s7yr@begin>
On Sun, Nov 26, 2023 at 08:32:30PM +0100, Samuel Thibault wrote:
> I found the issue, it's because of the quiescence support in libports,
> which assumes that all threads will sooner or later go through a
> quiescent state (because it finished processing a message). But that's
> not true, proc doesn't set a thread timeout, and thus some threads can
> stay indefinitely stuck in receiving messages. And thus the deferred
> dereferencing used by ports_destroy_right never gets achieved.
>
> I'll push a fix.
Very nice catch.
--
Richard Braun
Reply to: