From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Mikael Svahnberg Newsgroups: gmane.emacs.bugs Subject: bug#43882: 27.1; Gnus sometimes crashes emacs 27.1 during nnir search Date: Thu, 15 Oct 2020 09:26:45 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000a7394c05b1b092d3" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10604"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 43882@debbugs.gnu.org To: Robert Pluim Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Oct 15 09:31:10 2020 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 1kSxjC-0002eU-Kb for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 15 Oct 2020 09:31:10 +0200 Original-Received: from localhost ([::1]:42470 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kSxjB-0003kz-Cw for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 15 Oct 2020 03:31:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36398) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kSxj4-0003kp-Ez for bug-gnu-emacs@gnu.org; Thu, 15 Oct 2020 03:31:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42491) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kSxj4-00011R-4j for bug-gnu-emacs@gnu.org; Thu, 15 Oct 2020 03:31:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kSxj3-00050p-L3 for bug-gnu-emacs@gnu.org; Thu, 15 Oct 2020 03:31:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Mikael Svahnberg Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 15 Oct 2020 07:31:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 43882 X-GNU-PR-Package: emacs Original-Received: via spool by 43882-submit@debbugs.gnu.org id=B43882.160274703619236 (code B ref 43882); Thu, 15 Oct 2020 07:31:01 +0000 Original-Received: (at 43882) by debbugs.gnu.org; 15 Oct 2020 07:30:36 +0000 Original-Received: from localhost ([127.0.0.1]:54037 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kSxid-00050B-Uw for submit@debbugs.gnu.org; Thu, 15 Oct 2020 03:30:36 -0400 Original-Received: from mail-pj1-f44.google.com ([209.85.216.44]:51350) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kSxfC-0004t1-Fd for 43882@debbugs.gnu.org; Thu, 15 Oct 2020 03:27:03 -0400 Original-Received: by mail-pj1-f44.google.com with SMTP id a17so1317566pju.1 for <43882@debbugs.gnu.org>; Thu, 15 Oct 2020 00:27:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZwqHTtu24BzptCHt2cCwdT/Nv19j1QchAmUUP/cMpLE=; b=QtrIo0ou6cTVVeMpvvHchI3iBaGj//uOKCm1eK0x9hMRHnAgejTvBhSHWho2VUc4Fb Cz16nTsHuKBc6OdJ9fgJXSS7IZx3J0bDqJwpUcrsnLp2qZzlRcCUcBo4kK5DKwy9IXaD R03UrsiTmndgz3WmXbb4h64x1oJ80PzYUVismeS4SwhxKlXl+OTBisTwy4wdehwmZPVp 0wXwBAPEKOJCM6rAExjg4TBq6uKlaXIkvSLf8iyvryyaWPAgLNjcrl7DZc+XWM3LTWdr 96kw6T5sBGq8ryALmWVc+oqEiNn/Ix+ohYv6KMsM3j+BJqK5RytgRgQeDntMxNpSXiuQ CwQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZwqHTtu24BzptCHt2cCwdT/Nv19j1QchAmUUP/cMpLE=; b=QoP2dP8+njvXGGRPabKK/Wr8djLdZSVCc6CSQcUh8IZeTIAhxUh8axiPfeY8b5F/pq eTYidHg5SObW05l/e4im0Pv5yK0CCkl4mUk1LlQjEgn28EF3/kzv58qMxW6yS/6LFsoN NA3IlSqcZeRtaoeOIINvGu5vXKHzeMTYh3ydeKhcGD+8QKqTbVon3KcaQwW16zdeWONz QotXiueRIh9tP7U7nDll/jYyICPeBQJY88KD1oabnpeXAdGdss+toA1oBB18bQBc6zx+ FTgJJdB5FEvo7B6SSZu5ASSRICgbOi9n5PSHsDoKzne+H0j6+8P5SS3TnZ5YTLfAKePW LaGA== X-Gm-Message-State: AOAM532gPbP5eUuxCiMrUiJGCnkYJj1UsCoMKY4Z1SsoQvUjT8PJxtd6 MMFsPBZtfR0IB6E1qfUQNmd8/VTMfMjaApoVRAE= X-Google-Smtp-Source: ABdhPJz9lsibndB5KzrhSt52uYpBRhNelWWJATzMezpENrYDJ7oivcfM1a7SHJf6Pdlaop2GYV2Q2WC/AJGuJtqNWxk= X-Received: by 2002:a17:902:6b09:b029:d3:ec36:35fc with SMTP id o9-20020a1709026b09b02900d3ec3635fcmr3086934plk.4.1602746816345; Thu, 15 Oct 2020 00:26:56 -0700 (PDT) In-Reply-To: X-Mailman-Approved-At: Thu, 15 Oct 2020 03:30:34 -0400 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" Xref: news.gmane.io gmane.emacs.bugs:190548 Archived-At: --000000000000a7394c05b1b092d3 Content-Type: text/plain; charset="UTF-8" Hi, An update: I started emacs with the increased stack on Monday and have been working as normal since then except that I've been searching for e-mail a bit more often. Today (Thursday), emacs crashed on me again when I was searching for e-mail. Observations: - A few minutes before it started crashing I got a spinning beach ball for a few seconds while composing an e-mail. - The crash took much longer this time. I didn't time it, but maybe in the order of 10-15 minutes. - During this time I observed what I could think of through the Activity monitor: -- Emacs was consuming 100% CPU (of one CPU). -- It was eating memory at a rate of 5 MB every other second -- "Faults" and "UNIX system Calls" increased at a steady rate, but I have no idea where they started from or what is normal behaviour... Now, I am going to reduce the stack size again to force the issue and update to HEAD. Let's see if that makes any difference. /Mikael On Mon, 12 Oct 2020 at 11:45, Robert Pluim wrote: > >>>>> On Mon, 12 Oct 2020 09:12:56 +0200, Mikael Svahnberg < > Mikael.Svahnberg@bth.se> said: > >> Do things improve if you increase your stack size using 'ulimit -s'? > >> MacOS has what is by modern standards a fairly small default stack. > >> > >> There are a couple of regexp-related fixes in master as well. Could > >> you try that branch? > >> > >> Robert > > Mikael> Hi, > > Mikael> The stack size was the default 8192 kB. I have -- reluctantly, > but in > Mikael> the interest of debugging -- set it to 65532 kB via ulimit and > then > Mikael> launched emacs from that shell. > > Why reluctantly? 64M these days is nothing in terms of memory. > > Mikael> How can I verify from within Emacs what stack size it is > running with? > > You can't, but since you've launched emacs from that shell it will be > ok. > > Mikael> I will keep it like this for a couple of days and see if I get > more > Mikael> crashes. If I do, I will report and move on and upgrade to > HEAD. > > Thanks > > Robert > -- > --000000000000a7394c05b1b092d3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

An update: I started emacs with the= increased stack on Monday and have been working as normal since then excep= t that I've been searching for e-mail a bit more often.

<= div>Today (Thursday), emacs crashed on me again when I was searching for e-= mail.

Observations:
=C2=A0- A few minute= s before it started crashing I got a spinning beach ball for a few seconds = while composing an e-mail.
=C2=A0- The crash took much longer thi= s time. I didn't time it, but maybe in the order of 10-15 minutes.
=C2=A0- During this time I observed what I could think of through the= Activity monitor:
=C2=A0-- Emacs was consuming 100% CPU (of one = CPU).
=C2=A0-- It was eating memory at a rate of 5 MB every other= second
=C2=A0-- "Faults" and "UNIX system Calls&q= uot; increased at a steady rate, but I have no idea where they started from= or what is normal behaviour...


Now= , I am going to reduce the stack size again to force the issue and update t= o HEAD. Let's see if that makes any difference.

/Mikael

On Mon, 12 Oct 2020 at 11:45, Robert Pluim <rpluim@gmail.com> wrote:
>>>>> On Mon, 1= 2 Oct 2020 09:12:56 +0200, Mikael Svahnberg <Mikael.Svahnberg@bth.se> said:
=C2=A0 =C2=A0 >> Do things improve if you increase your stack size us= ing 'ulimit -s'?
=C2=A0 =C2=A0 >> MacOS has what is by modern standards a fairly small= default stack.
=C2=A0 =C2=A0 >>
=C2=A0 =C2=A0 >> There are a couple of regexp-related fixes in master= as well. Could
=C2=A0 =C2=A0 >> you try that branch?
=C2=A0 =C2=A0 >>
=C2=A0 =C2=A0 >> Robert

=C2=A0 =C2=A0 Mikael> Hi,

=C2=A0 =C2=A0 Mikael> The stack size was the default 8192 kB. I have -- = reluctantly, but in
=C2=A0 =C2=A0 Mikael> the interest of debugging -- set it to 65532 kB vi= a ulimit and then
=C2=A0 =C2=A0 Mikael> launched emacs from that shell.

Why reluctantly? 64M these days is nothing in terms of memory.

=C2=A0 =C2=A0 Mikael> How can I verify from within Emacs what stack size= it is running with?

You can't, but since you've launched emacs from that shell it will = be
ok.

=C2=A0 =C2=A0 Mikael> I will keep it like this for a couple of days and = see if I get more
=C2=A0 =C2=A0 Mikael> crashes. If I do, I will report and move on and up= grade to HEAD.

Thanks

Robert
--
--000000000000a7394c05b1b092d3--