From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pedro Andres Aranda Gutierrez Newsgroups: gmane.emacs.bugs Subject: bug#70049: 30.0.50; (server-running-p) in mode line freezes emacs Date: Fri, 29 Mar 2024 08:09:37 +0100 Message-ID: References: <8634sah952.fsf@gnu.org> <86jzlmfhl5.fsf@gnu.org> <867chlfrwt.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000287f3e0614c7546f" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19262"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 70049@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Mar 29 08:11:26 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rq6Ob-0004re-SQ for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 29 Mar 2024 08:11:26 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rq6OE-00077S-Ez; Fri, 29 Mar 2024 03:11:02 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rq6OD-00076c-9F for bug-gnu-emacs@gnu.org; Fri, 29 Mar 2024 03:11:01 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rq6OD-00013t-12 for bug-gnu-emacs@gnu.org; Fri, 29 Mar 2024 03:11:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rq6OD-00032f-Sw for bug-gnu-emacs@gnu.org; Fri, 29 Mar 2024 03:11:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Pedro Andres Aranda Gutierrez Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 29 Mar 2024 07:11:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 70049 X-GNU-PR-Package: emacs Original-Received: via spool by 70049-submit@debbugs.gnu.org id=B70049.171169621911408 (code B ref 70049); Fri, 29 Mar 2024 07:11:01 +0000 Original-Received: (at 70049) by debbugs.gnu.org; 29 Mar 2024 07:10:19 +0000 Original-Received: from localhost ([127.0.0.1]:41595 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rq6NU-0002xZ-KW for submit@debbugs.gnu.org; Fri, 29 Mar 2024 03:10:18 -0400 Original-Received: from mail-ed1-x536.google.com ([2a00:1450:4864:20::536]:43388) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rq6NO-0002wB-WE for 70049@debbugs.gnu.org; Fri, 29 Mar 2024 03:10:14 -0400 Original-Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-565c6cf4819so4644665a12.1 for <70049@debbugs.gnu.org>; Fri, 29 Mar 2024 00:10:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711696203; x=1712301003; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=wNTIOEQtjtYXiw+YP3ArUa6KbZ3T/WhTL003YPlPa9Y=; b=bwHhfy79thZ5w8N95c4LOlLffveL+EcIffOGGNtxWdMYjF/ywlsdMU9WyoylsZXXjZ MdIv8Q6a9XwhzjC2//HTnvLtu5AgAwxO5ZvXoSvElznZnOLsGwsnDX0SDJokjkrs9TEp xX54oHuoIly0/DhTBu0fEib49lsoF6RM7WX5bLTjWkBUPWqVEACjEbROuUJjLEpB45Uf HCJbA/KsbR3o28Gd1sB15Ww1AuoYl/41ShasF6qNTTQeY2lw+ZMKQu0rwJJBvQeLmasM 7PPZVZ+sEG8I168JKuxyTCe4lekttIOC12FUrU7qG6fb0g4h1FL8ylk4t8D9gSQqOi9e DhDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711696203; x=1712301003; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=wNTIOEQtjtYXiw+YP3ArUa6KbZ3T/WhTL003YPlPa9Y=; b=BTi+PQkYqz+VKnvuK/ArPt8kEmUPHOqpKgyPu/ppY3KTjNS99xXWhuXvpCemhLCagb Ib0wxHITCHDOtI1iEYl9IGxhvX2JE4WMAE0iJ5OS3yIeTiMrszC10G2eC2/e5YG4F6p9 4a0mkWCyCUZtRtnN6bRLylb4wve0o51Kw5/tqUF20PkC+8fWNohKV8vViSNmzkdfjNCf 1M7PqOybqfGcDGP6OUB6/Njp0dhA9PyH+g5y1hqWYeODw+VD2Aqo4K3W9Hnuochr70bT w7Be/W0VZmFVNtNKEFrZbjp0CSdoaGleRZJ5MfiXdeFRVI2EDz2w2mTzqbeUid4ECQNq ftuQ== X-Gm-Message-State: AOJu0YyR+HtbRb9ETcLu4mymAnaSyFv51H/eL6lT8bT/vg8QzzZvsgX+ 9XFJ6go7VCjgcHKNndJ/N7asCVBZxR5RnReBa8q8gT6h4Lu7GpGh9V3i6IvtkazYEXIWqMSY9O5 /rfX54LoxRU2KceYUPgH+me/rxUM= X-Google-Smtp-Source: AGHT+IHQYq8vjdmOuqI7R06iHlHvuEWzynsO17cWuoewhbCQCp8vsLNz0z2ZfdLr1VUY2/1v5QSo6p77Vw8tGr1sAk4= X-Received: by 2002:a05:6402:26c3:b0:56c:16c9:cb00 with SMTP id x3-20020a05640226c300b0056c16c9cb00mr1621564edd.12.1711696203249; Fri, 29 Mar 2024 00:10:03 -0700 (PDT) In-Reply-To: <867chlfrwt.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:282272 Archived-At: --000000000000287f3e0614c7546f Content-Type: text/plain; charset="UTF-8" Hi Eli, that may tabe a bit longer... I'm creating a .deb in a VM which I then install on my system(s). But on it! Best, /PA On Fri, 29 Mar 2024 at 07:55, Eli Zaretskii wrote: > > From: Pedro Andres Aranda Gutierrez > > Date: Fri, 29 Mar 2024 07:37:32 +0100 > > Cc: 70049@debbugs.gnu.org > > > > Can you look at the CPU meter and tell if Emacs consumes CPU in this > > state or not? > > > > I've fired up the system monitor on my Ubuntu 22.04. waited the CPU > curves stabilised before activating > > server-mode, > > then waited again until everything was quiet again and then resized > Emacs to trigger the 'Emacs is not > > responding' > > dialog. There was no significant raise in CPU or memory consumption. > Then repeated the same with the > > process tab > > and couldn't detect any significant change. > > OK, thanks. This means Emacs is waiting for something. > > Can you provide the GDB backtrace from this situation? To do this, > repeat your sequence that causes Emacs to freeze, then do the > following from a separate shell prompt: > > $ cd /path/to/emacs/src > $ gdb -p PID > GNU gdb (GDB) XY.Z > Copyright (C) NNNN Free Software Foundation, Inc. > ... > (gdb) source .gdbinit > (gdb) thread apply all bt > > where PID is the process ID of the frozen Emacs process, and > /path/to/emacs/src is the absolute file name of the directory where > you have the Emacs C source files -- there is a .gdbinit file there > which will cause GDB to produce both C and Lisp backtrace when you > type the "bt" command at the (gdb) prompt. > > Then post the results here. > > Thanks. > -- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Headaches with a Juju log: unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run a leader-deposed hook here, but we can't yet --000000000000287f3e0614c7546f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Eli,=C2=A0

that may tabe a bit longe= r... I'm creating a .deb in a VM which I then install on my system(s).<= div>But on it!

Best, /PA

On Fri, 29 Mar= 2024 at 07:55, Eli Zaretskii <eliz@gnu.= org> wrote:
> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> Date: Fri, 29 Mar 2024 07:37:32 +0100
> Cc: 70049@d= ebbugs.gnu.org
>
>=C2=A0 Can you look at the CPU meter and tell if Emacs consumes CPU in = this
>=C2=A0 state or not?
>
> I've fired up the system monitor on my Ubuntu 22.04. waited the CP= U curves stabilised before activating
> server-mode,
> then waited again until everything was quiet again and then resized Em= acs to trigger the 'Emacs is not
> responding'
> dialog. There was no significant raise in CPU or memory consumption. T= hen repeated the same with the
> process tab
> and couldn't detect any significant change.

OK, thanks.=C2=A0 This means Emacs is waiting for something.

Can you provide the GDB backtrace from this situation?=C2=A0 To do this, repeat your sequence that causes Emacs to freeze, then do the
following from a separate shell prompt:

=C2=A0 $ cd /path/to/emacs/src
=C2=A0 $ gdb -p PID
=C2=A0 GNU gdb (GDB) XY.Z
=C2=A0 Copyright (C) NNNN Free Software Foundation, Inc.
=C2=A0 ...
=C2=A0 (gdb) source .gdbinit
=C2=A0 (gdb) thread apply all bt

where PID is the process ID of the frozen Emacs process, and
/path/to/emacs/src is the absolute file name of the directory where
you have the Emacs C source files -- there is a .gdbinit file there
which will cause GDB to produce both C and Lisp backtrace when you
type the "bt" command at the (gdb) prompt.

Then post the results here.

Thanks.


--
Fragen sind nicht da, um bea= ntwortet zu werden,
Fragen sind da um gestellt zu werden
= Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should ru= n a leader-deposed hook here, but we can't yet

 --000000000000287f3e0614c7546f--