From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Pip Cet Newsgroups: gmane.emacs.bugs Subject: bug#39962: 27.0.90; Crash in Emacs 27.0.90 Date: Thu, 19 Mar 2020 19:31:44 +0000 Message-ID: References: <24162.58107.725366.668639@cochabamba.vanoostrum.org> <83y2s48yn7.fsf@gnu.org> <83zhck6obg.fsf@gnu.org> <83r1xv73ze.fsf@gnu.org> <83imj5bdct.fsf@gnu.org> <83zhcff131.fsf@gnu.org> <2b2fc990-2917-7970-d88b-7708dbaa48be@cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="83024"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Robert Pluim , Paul Eggert , 39962@debbugs.gnu.org To: Pieter van Oostrum Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Mar 19 20:33:11 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 1jF0ul-000LWX-BL for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 19 Mar 2020 20:33:11 +0100 Original-Received: from localhost ([::1]:42138 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jF0uk-00042Y-AY for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 19 Mar 2020 15:33:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57837) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jF0ud-00042S-9N for bug-gnu-emacs@gnu.org; Thu, 19 Mar 2020 15:33:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jF0uc-0005Fj-AW for bug-gnu-emacs@gnu.org; Thu, 19 Mar 2020 15:33:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:37673) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jF0uc-0005Ew-53 for bug-gnu-emacs@gnu.org; Thu, 19 Mar 2020 15:33:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jF0uc-0001Sw-0q for bug-gnu-emacs@gnu.org; Thu, 19 Mar 2020 15:33:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Pip Cet Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 19 Mar 2020 19:33:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 39962 X-GNU-PR-Package: emacs Original-Received: via spool by 39962-submit@debbugs.gnu.org id=B39962.15846463495591 (code B ref 39962); Thu, 19 Mar 2020 19:33:01 +0000 Original-Received: (at 39962) by debbugs.gnu.org; 19 Mar 2020 19:32:29 +0000 Original-Received: from localhost ([127.0.0.1]:43646 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jF0u5-0001S5-0N for submit@debbugs.gnu.org; Thu, 19 Mar 2020 15:32:29 -0400 Original-Received: from mail-ot1-f49.google.com ([209.85.210.49]:32916) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jF0u2-0001Rq-Jp for 39962@debbugs.gnu.org; Thu, 19 Mar 2020 15:32:27 -0400 Original-Received: by mail-ot1-f49.google.com with SMTP id x26so3680578otk.0 for <39962@debbugs.gnu.org>; Thu, 19 Mar 2020 12:32:26 -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=hfGy6Ij/2gpRfGAdrsbl1HGh/HC673BYi2t6RooIHsc=; b=WiwC05MwckfcuXHvBok47ExfARY3qWvpgoRhUa1/kGBb0p/R/PYSMc/iGrvMqLF35l Dln0GTGgX2QgrXdSdo/BXuQyt//X09uMVngXRKX5ImDkIc3EKbr0syBw3ApUhElH6V05 KvBCWJJQ0Qt5MQrdsoOuXCVF8DLN63kL9uGWfQQ+5gP1r6iWCHPRdNEDurDTh/VsyN20 oySmL7uVomKHVc7ZHaqy89/wVIeFwFk0qeBfdFuiQmWgsezaq9xQ68VCZ5KIBug17snu EnQFvJTYNF51T8Zpbhb65Uj7DFMGXaTgNzYODnHAN9RFZXX07P3mJj/X6AYHEMQC0Sy2 UhEA== 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=hfGy6Ij/2gpRfGAdrsbl1HGh/HC673BYi2t6RooIHsc=; b=rKo5wiS5fd6Ye9bQB47Q9QhOWSTK5By2hEkxxYI6D+msMIZH5edEKjOMrC3ZOKETLD lT5euk6ll1BFfeuYGHaNl+ZWaLfr9oFeJnhWip9vZt9djA1+c85cbRbb8I4Qs7TN2jfW FFwX0tMrJy9L5x1QuRboJI4xjVcM0eLBXkh23HlpGI2C1+AELlvCxUk8dw/kzfGzC2J6 yk4qUv9IXvKY8XZvXynr6HoHTYbF8OggdlImFlg7OQPxIMOG9o+ProJZPSY4p8vckNDs 8BydbLlbh2xgPVrdNDF/DuUsKSpmuVcn/klWctODAarZj3iZAGxvJRlH3o/b9uXJzDRz w7Zg== X-Gm-Message-State: ANhLgQ2bo729kDCALePBVWwZV0W749gJPRs/oXokn4ulGmwvzwd0DJQf AxK5TXEN9OTheRGWDkUxps7qDLRtEnRZ48tWdwY= X-Google-Smtp-Source: ADFU+vuagpA4ZjvAfeaw2iIz9EmBOarmQIKQHUozPVeeoEn1sEFIvGbnuzrVc/oEGb2/yhHjiP6rWv3oUmhtI979K+4= X-Received: by 2002:a05:6830:110c:: with SMTP id w12mr3429882otq.175.1584646341014; Thu, 19 Mar 2020 12:32:21 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 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:177550 Archived-At: On Thu, Mar 19, 2020 at 7:17 PM Pieter van Oostrum wrote: > I had my keyboard macro translated to an Elisp function and then called this a 100 times with dotimes. However, there was no crash, even though I had the smaller stack size. > > In total I had the macro run some 300+ times without any crash. I just had it run automatically (put it in a .el file, and used emacs -Q -l testfile.el), so no keyboard/mouse interaction. Did you use emacs -Q to produce the original crash, or just emacs? I ask because it's possible something in your mode line specification caused or exacerbated the problem. > > If I'm right, it should be possible to trigger the bug by creating a > > reasonably large session, running (garbage-collect) in an infinite > > loop, and interacting with the mouse and keyboard while that is > > happening. Or running your keyboard macro in a similar loop, of > > course. > > But if I do it in a loop it will not react to the keyboard/mouse. Do you think the asynchronous processing of these events will be sufficient, even though no action is taken on these events? I think so, but I'm not sure. I've been looking at this code for a while, and I think the likeliest culprit is the mouse-over highlighting code, possibly for the mode line. On GNU/Linux, the behavior is quite odd: for the first second or so after starting a loop, the mode line elements react to mouseover events, but not afterwards. On the other hand, a millisecond delay ought to be enough to catch it during the first second.