From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Alex Branham Newsgroups: gmane.emacs.bugs Subject: bug#37000: 27.0.50; gc and laggy Emacs Date: Thu, 15 Aug 2019 09:56:44 -0500 Message-ID: <87v9uywk7n.fsf@gmail.com> References: <87a7ch9ea6.fsf@gmail.com> <837e7l7ymr.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="191876"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: 37000@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Aug 15 16:57:32 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hyHBz-000ndS-3N for geb-bug-gnu-emacs@m.gmane.org; Thu, 15 Aug 2019 16:57:31 +0200 Original-Received: from localhost ([::1]:42760 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hyHBw-00056O-Ni for geb-bug-gnu-emacs@m.gmane.org; Thu, 15 Aug 2019 10:57:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33198) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hyHBa-00051p-Se for bug-gnu-emacs@gnu.org; Thu, 15 Aug 2019 10:57:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hyHBX-0006Tf-BT for bug-gnu-emacs@gnu.org; Thu, 15 Aug 2019 10:57:06 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:43382) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hyHBX-0006TX-8C for bug-gnu-emacs@gnu.org; Thu, 15 Aug 2019 10:57:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hyHBX-0004ai-4G for bug-gnu-emacs@gnu.org; Thu, 15 Aug 2019 10:57:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Alex Branham Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 15 Aug 2019 14:57:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 37000 X-GNU-PR-Package: emacs Original-Received: via spool by 37000-submit@debbugs.gnu.org id=B37000.156588101317604 (code B ref 37000); Thu, 15 Aug 2019 14:57:03 +0000 Original-Received: (at 37000) by debbugs.gnu.org; 15 Aug 2019 14:56:53 +0000 Original-Received: from localhost ([127.0.0.1]:52198 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hyHBM-0004Zs-Ql for submit@debbugs.gnu.org; Thu, 15 Aug 2019 10:56:53 -0400 Original-Received: from mail-oi1-f172.google.com ([209.85.167.172]:39445) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hyHBL-0004ZX-5T for 37000@debbugs.gnu.org; Thu, 15 Aug 2019 10:56:51 -0400 Original-Received: by mail-oi1-f172.google.com with SMTP id 16so2323384oiq.6 for <37000@debbugs.gnu.org>; Thu, 15 Aug 2019 07:56:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=ubnAgViCJ5UTHVOP6J33QMhFya9J9l3Usz3SbsmjF7A=; b=K6Y+8iypaeu8JdgDfY7YzhEb9a0h6ZSww5SSwKUjcAHjbZrW9mxm3jl4gD43SU4MHj zrQ3KRBNZPT7+d5zdRoKWPy7xkVZIqJgfnnDtDO9N+eqojGjyacZnF/GcwNDgNgtO62b G1hfnBv3NYi/7TXdvcMKGdp1babW6lRwKGq2YxcNed3TJLqnDbT7RSQ0ooZjpa27Qg7S fletl6XR4oqbf2z00/iM2tLsgOFSsQnXk4+efJHrBcDs0R751+JNq3GxUv3txsPEzkF7 z57Q/2CjmqLj54EmqYBMIpm9rqrwypsENYSAOg3TsnV0QJnd092RczCm8u7ndGjr6kSQ eESQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=ubnAgViCJ5UTHVOP6J33QMhFya9J9l3Usz3SbsmjF7A=; b=tvumyA75Pkn98FzZsWgvk7yD8xsqT9hggoDPNceuZII86e3JkkOhRtJJvmUZdrFhej SmxCuRySL3yfp9LcetNyh262eaB+1/7KFQswQIRUj7P006d88/rCUTI+oTjbapjx5qw9 +4MN5h0RmLMekbIEc761uxQ3PI59shrVxiTNzaqmJ4+C38EsUNBDFtXJtrFcrD0xMLxV b4AcXW35l87GP9e53q1rQV9crljRkWEHz4ITBN0oLZpfU64wj7DwtMY0Ep4d6Jno3pyz 8VgaXf97c30RUH6RgC9W+U8lo/7H1OrUfSrk+dnTvmWRARBCkjHH+lQLxhuFn0b8SiuR HsoQ== X-Gm-Message-State: APjAAAXwxUqjECN8oN/CHdt8Dm3Z7q5f8GGTjPf5JI5BMa4WbqkTaabs A0ElCLMgwRmQ2JpngpnJNjt6dthhjRI= X-Google-Smtp-Source: APXvYqyrm2XEKiCzKuHhZjryWmBrvF0I9Ok/DCctRNeuFHaPoGAZv732+54XMIBPoNuR/YzMTCIWbw== X-Received: by 2002:aca:c50a:: with SMTP id v10mr1905376oif.174.1565881005271; Thu, 15 Aug 2019 07:56:45 -0700 (PDT) Original-Received: from earth (cpe-70-114-192-208.austin.res.rr.com. [70.114.192.208]) by smtp.gmail.com with ESMTPSA id q24sm1084998otl.31.2019.08.15.07.56.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 15 Aug 2019 07:56:44 -0700 (PDT) In-Reply-To: <837e7l7ymr.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 10 Aug 2019 19:50:52 +0300") 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:165107 Archived-At: On Sat 10 Aug 2019 at 19:50, Eli Zaretskii wrote: >> From: Alex Branham >> Date: Sat, 10 Aug 2019 11:27:29 -0500 >> >> Recently I've noticed Emacs sometimes getting _very_ laggy, as in >> taking up to a half-second to display the a single character that >> I type. M-x profiler-start suggests that garbage-collection is >> taking up too much time (see below my signature for example >> output). gc-cons-percentage and gc-cons-threshold are at their >> default values. I can't figure out how to reproduce this reliably, >> but running M-x relint-directory on the Emacs source tree seems to >> do a decent job triggering it. My Emacs is built from commit >> 4ce9c6d0b58bd77bc811d6c1c5caf955a5a0be2f (~ 4 days ago) of the >> master branch. How can I go about tracking this down? > > Trying to bisect to find the offending commit would be one way. Thanks. I noticed there's some activity around gc on master currently. I'll wait for that to pass before trying this. I'll note though that I don't see this issue on 26.2. Alex