| delorie.com/archives/browse.cgi | search |
| DMARC-Filter: | OpenDMARC Filter v1.4.2 delorie.com 686Bd7GA287489 |
| Authentication-Results: | delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com |
| Authentication-Results: | delorie.com; spf=pass smtp.mailfrom=cygwin.com |
| DKIM-Filter: | OpenDKIM Filter v2.11.0 delorie.com 686Bd7GA287489 |
| Authentication-Results: | delorie.com; |
| dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=Py572HZT | |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| DKIM-Filter: | OpenDKIM Filter v2.11.0 sourceware.org ED9AA4BBCDE2 |
| DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; |
| s=default; t=1788694745; | |
| bh=zdMN5gL/DuufEIV6p8lxHNtWJ5LwvOTU3qGpDsr/Ptk=; | |
| h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: | |
| List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: | |
| From; | |
| b=Py572HZTbbQ0xbUEKTxRGLw0QowhrMP+3/LeNqerPWAqlsIyirWt8gxZUfSKSKByv | |
| rgwWcz0q9OVtaV5klJfD5tdAeIc4zXZTZj3A4uDRuQ3E/2p857vMSWEsGyVO6uHP1l | |
| dqrl6zqUpcGaSnr8BfL1eKcGS9yXZJA4XFOH9jm4= | |
| X-Original-To: | cygwin AT cygwin DOT com |
| Delivered-To: | cygwin AT cygwin DOT com |
| DMARC-Filter: | OpenDMARC Filter v1.4.2 sourceware.org 645EF4BB1C3A |
| ARC-Filter: | OpenARC Filter v1.0.0 sourceware.org 645EF4BB1C3A |
| ARC-Seal: | i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1788694696; cv=none; |
| b=KN/S6hjCDjMmpnFj5gwI+QT0sUdtRRuySKyfUn8g1cdDANsS2einyNmROK3BPBncyqTrza5B9I/Zhcxgg/Wt30RhhA6bb1ZcKuJYMQR/0yhnr2i/qfrj5Czt9Z07XjLLf7XSVgDa03Ic8fCZG17iqKBUG10GMzMpJqplmVmPQLg= | |
| ARC-Message-Signature: | i=1; a=rsa-sha256; d=sourceware.org; s=key; |
| t=1788694696; c=relaxed/simple; | |
| bh=ECKaCaodtkZRP0jv3NoPHeT6H5BE0/tkFWALJIUYlus=; | |
| h=Date:From:To:Subject:Message-Id:Mime-Version:DKIM-Signature; | |
| b=GTc01KRdof1gMopRVAn+PfYJ/4xDIycpJNna6fmR6LFdRZMac6ThQFVaicF8zZm8DVhlz64nYqQr0wKKvFeD9ZqlS4VQ4SjuOYE0qFfcazfMfBK7OyJu4Q5sSVup7DhvH74pPPU2aBMUCX07blhOwukByUOAeLeVuzGwSP/XSK4= | |
| ARC-Authentication-Results: | i=1; sourceware.org; |
| dkim=pass (2048-bit key, unprotected) | |
| header.d=nifty.ne.jp header.i=@nifty.ne.jp header.a=rsa-sha256 | |
| header.s=default-1th84yt82rvi header.b=tpSXg9W8 | |
| DKIM-Filter: | OpenDKIM Filter v2.11.0 sourceware.org 645EF4BB1C3A |
| Date: | Sun, 6 Sep 2026 20:38:11 +0900 |
| To: | cygwin AT cygwin DOT com |
| Subject: | Re: btop 1.4.7 info panes freeze |
| Message-Id: | <20260906203811.08a1468e642b00b64b1db7f2@nifty.ne.jp> |
| In-Reply-To: | <9dd7ca7f-c2dd-4efc-890f-7051aec77385@SystematicSW.ab.ca> |
| References: | <126dcd3a-1d77-4c00-a267-2c72125b9b7a AT Shaw DOT ca> |
| <20260902155008 DOT 5de9bc63596105891d6bed31 AT nifty DOT ne DOT jp> | |
| <0a15c0d8-af04-4d65-916d-0e65d99c94de AT SystematicSW DOT ab DOT ca> | |
| <20260904055859 DOT f987264415d4608af0a48b9c AT nifty DOT ne DOT jp> | |
| <9dd7ca7f-c2dd-4efc-890f-7051aec77385 AT SystematicSW DOT ab DOT ca> | |
| X-Mailer: | Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) |
| Mime-Version: | 1.0 |
| X-BeenThere: | cygwin AT cygwin DOT com |
| X-Mailman-Version: | 2.1.30 |
| List-Id: | General Cygwin discussions and problem reports <cygwin.cygwin.com> |
| List-Unsubscribe: | <https://cygwin.com/mailman/options/cygwin>, |
| <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe> | |
| List-Archive: | <https://cygwin.com/pipermail/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-request AT cygwin DOT com?subject=help> |
| List-Subscribe: | <https://cygwin.com/mailman/listinfo/cygwin>, |
| <mailto:cygwin-request AT cygwin DOT com?subject=subscribe> | |
| From: | Takashi Yano via Cygwin <cygwin AT cygwin DOT com> |
| Reply-To: | Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp> |
| Errors-To: | cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com |
| Sender: | "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com> |
Hi Brian,
On Fri, 4 Sep 2026 10:44:51 -0600
Brian Inglis wrote:
> On 2026-09-03 14:58, Takashi Yano via Cygwin wrote:
> > Hi Brian,
> >
> > On Wed, 2 Sep 2026 12:52:53 -0600
> > Brian Inglis wrote:
> >> On 2026-09-02 00:50, Takashi Yano via Cygwin wrote:
> >>> On Tue, 1 Sep 2026 23:24:27 -0600
> >>> Brian Inglis wrote:
> >>>> Now with btop 1.4.7 it is less obvious when it freezes, as the info panes become
> >>>> static, while the time display keeps updating, whereas in the previous release,
> >>>> the time display also froze, making the need for a restart more obvious.
> >>>
> >>> Thanks for the report. Two questions.
> >>> (1) When btop freezes, are all the info panes stopped,
> >>> while the time on the top middle is updating?
> >>
> >> As far as I can tell, nothing else, other than the top middle timestamp (update
> >> period 60000ms), is being obviously updated e.g. uptime freezes.
> >>
> >>> (2) How often the issue happens?
> >>
> >> It happens every few days: Cygwin services run continuously between Cygwin Setup
> >> upgrade runs or Windows patch restarts (the weekend before Patch Tuesdays).
> >> I stay logged in running Xwin between those Cygwin startups.
> >
> > Are there any error messages in ~/.local/state/btop.log?
> Ah - didn't know about that: attached log entries since just before the upgrade
> from 1.4.5 to 1.4.7, then -2 on Sep 3.
> Now going to download and install -3 and keep an eye on that log.
> 2026/08/10 (02:33:15) | ERROR: Stall in Runner thread, restarting!
> 2026/08/11 (22:02:06) | ERROR: Stall in Runner thread, restarting!
> 2026/08/13 (12:14:06) | ERROR: Stall in Runner thread, restarting!
These are the problem that Claude expected. The mechanism of
the freeze is as follows.
(1) Due to high load of the system, the runner thread in btop
sometimes does not respond in predetermined period.
(2) If the main thread detects that runner thread hang, it
calls pthread_cancel() for runner thread to restart the
thread.
(3) However, if the runner thread holds a mutex, the thread
is cancelled without releasing mutex.
(4) The new runner thread freezes because it cannot acquire
the mutex.
On Linux, If the thread holding c++ mutex is cancelled, the
mutex is released in the unwinding process. However, cygwin
does not do that (POSIX does not require that).
1.4.7-3 do not call pthread_cancel() even when the response
from the runnder thread is delayed. Instead, simply skips
updating panes. Hopefully, 1.4.7-3 no longer suffers from
the issue.
--
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
| webmaster | delorie software privacy |
| Copyright © 2026 by DJ Delorie | Updated Sep 20 2026 |