From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.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, 27 Aug 2020 16:57:33 -0400 Message-ID: <87lfhzolhe.fsf@gmail.com> References: <87a7ch9ea6.fsf@gmail.com> <837e7l7ymr.fsf@gnu.org> <87v9uywk7n.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31743"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Cc: 37000-done@debbugs.gnu.org To: Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Aug 27 22:58: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 1kBOyI-00089i-7R for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 27 Aug 2020 22:58:10 +0200 Original-Received: from localhost ([::1]:43902 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kBOyH-00045l-5j for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 27 Aug 2020 16:58:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54596) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kBOyA-00044q-Hk for bug-gnu-emacs@gnu.org; Thu, 27 Aug 2020 16:58:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:60945) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kBOyA-00044G-97 for bug-gnu-emacs@gnu.org; Thu, 27 Aug 2020 16:58:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kBOyA-0001vn-8z for bug-gnu-emacs@gnu.org; Thu, 27 Aug 2020 16:58:02 -0400 Resent-From: Alex Branham Original-Sender: "Debbugs-submit" Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Thu, 27 Aug 2020 20:58:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 37000 X-GNU-PR-Package: emacs Mail-Followup-To: 37000@debbugs.gnu.org, alex.branham@gmail.com, alex.branham@gmail.com Original-Received: via spool by 37000-done@debbugs.gnu.org id=D37000.15985618647394 (code D ref 37000); Thu, 27 Aug 2020 20:58:02 +0000 Original-Received: (at 37000-done) by debbugs.gnu.org; 27 Aug 2020 20:57:44 +0000 Original-Received: from localhost ([127.0.0.1]:44256 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kBOxs-0001vB-7m for submit@debbugs.gnu.org; Thu, 27 Aug 2020 16:57:44 -0400 Original-Received: from mail-qt1-f196.google.com ([209.85.160.196]:40587) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kBOxp-0001ux-Og for 37000-done@debbugs.gnu.org; Thu, 27 Aug 2020 16:57:42 -0400 Original-Received: by mail-qt1-f196.google.com with SMTP id s16so5778408qtn.7 for <37000-done@debbugs.gnu.org>; Thu, 27 Aug 2020 13:57:41 -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=mqQLM5iKnUFjXm6fz2t89vd1wyoyVVCBmue5ZS+2oF0=; b=MqsErVsx2dyDYJZp0fzBazYNl9HRHbcvTi6acDcKyk6Sd5+g7hchFIakUGtGuS7Z5Q Z9EplyE41XkCn3CZNO0v+snU8w4TuCSWvxQx+JRZhvjnSkKq0h2xUnFuRa72Iq1cYQEE 6eHoYbq/BUSTFKW3iiKOzyrHT0xvxf46s8eMPj7zcRpmraoBQ878akrE0LAQYO7WMh0K j10fhHAYIt5iUoFICq/jSw1rvOcQKRvaZjN1JwZpt5EKS55hnAF0SDJxft4K8Ask4lB/ 1QJpktXB6gXhiIpoN0ItqyfpZGsQfdtrIq6ao/MSv6fsd76cNaJs3BxfnEQsilOG/alr dQlQ== 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=mqQLM5iKnUFjXm6fz2t89vd1wyoyVVCBmue5ZS+2oF0=; b=an3mv6W1Raj5gJSk7n1VJ3SqYAK39ReA4Ipu0y4jXXFM/j88ZOjrMPzaTnhJTpC0E6 VlYFWPKSBQ+ThPwUCLdcB2VkI7EqC+h1dYII5JZErq0KsyzsgfWpfB+CvX0vHk6jp8v0 J+dm+iChXnbYiKsY0WG+dL9inbQsVXlqEnVnRS2KOD8+//NGhHg7MCXYac+GIrJtd7ZE n4d51OjenzSpTkjZAs9ttzJ846U6d7KTGu9E088Y21oImE/mtq0DAlDIvc8ejJ56SYFG 1ZiHxCjCMuBakb3ZTgZAghkGgNjRusxVGYdT64g9xqB/wlnL+Qmb9L5nG4OI7V+JO1Uk hDsg== X-Gm-Message-State: AOAM531XLVSqXnxqid4+flIpHCA6n0Jvb9pYVH0biHpNYgBw9hPZC+Wp DVErhIJDAjDWvCJJ/NuvYeDgUCTIslQ= X-Google-Smtp-Source: ABdhPJw4g5Au+GAj3G3ZQs37IxeEnTXVt3HRu0NtqWs1hX8XxfCRrEFK9Mq70dMxXBlSmo/ewlffzw== X-Received: by 2002:aed:3882:: with SMTP id k2mr7899512qte.308.1598561855738; Thu, 27 Aug 2020 13:57:35 -0700 (PDT) Original-Received: from earth (c-73-163-194-78.hsd1.dc.comcast.net. [73.163.194.78]) by smtp.gmail.com with ESMTPSA id h199sm2393214qke.112.2020.08.27.13.57.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 27 Aug 2020 13:57:34 -0700 (PDT) In-Reply-To: (Stefan Kangas's message of "Tue, 25 Aug 2020 17:15:33 -0700") 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:186568 Archived-At: On Tue 25 Aug 2020 at 17:15, Stefan Kangas wrote: > Alex Branham writes: > >> 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. > > (That was one year ago.) > > Any updates here? No, but the problem seems to have gone away so I'll close this bug.