From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.bugs Subject: bug#39413: 26.2; Emacs gets hung Date: Mon, 25 May 2020 08:15:29 -0400 Message-ID: <87sgfojjmm.fsf@gmail.com> References: <85r1ynam0x.fsf@gmail.com> <44e850a0-c8dc-4aec-5706-c52db33697a1@ubin.jp> <119c5df5-080e-c45b-6498-2a2bc0f8273b@yk.rim.or.jp> <83lfme232a.fsf@gnu.org> <0b9cd846-b9f5-8351-5f45-5614bbc644c0@ubin.jp> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="23601"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.91 (gnu/linux) Cc: 39413@debbugs.gnu.org To: chiaki-ishikawa-thunderbird-account Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon May 25 14:16:09 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 1jdC1Z-00061y-AM for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 25 May 2020 14:16:09 +0200 Original-Received: from localhost ([::1]:57838 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jdC1Y-0007lW-9T for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 25 May 2020 08:16:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35624) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jdC1S-0007lC-8C for bug-gnu-emacs@gnu.org; Mon, 25 May 2020 08:16:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:56800) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jdC1R-0001vs-Ty for bug-gnu-emacs@gnu.org; Mon, 25 May 2020 08:16:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jdC1R-0006Tw-PF for bug-gnu-emacs@gnu.org; Mon, 25 May 2020 08:16:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Noam Postavsky Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 25 May 2020 12:16:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 39413 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: unreproducible Original-Received: via spool by 39413-submit@debbugs.gnu.org id=B39413.159040893824886 (code B ref 39413); Mon, 25 May 2020 12:16:01 +0000 Original-Received: (at 39413) by debbugs.gnu.org; 25 May 2020 12:15:38 +0000 Original-Received: from localhost ([127.0.0.1]:40113 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jdC13-0006TK-Tc for submit@debbugs.gnu.org; Mon, 25 May 2020 08:15:38 -0400 Original-Received: from mail-qt1-f170.google.com ([209.85.160.170]:36139) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jdC12-0006T7-DP for 39413@debbugs.gnu.org; Mon, 25 May 2020 08:15:36 -0400 Original-Received: by mail-qt1-f170.google.com with SMTP id v4so13636973qte.3 for <39413@debbugs.gnu.org>; Mon, 25 May 2020 05:15:36 -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=B4X15ZN/wgvehnQbMInx5u21dSpO/o/y6oKeSSXY7i4=; b=aKV+WIsGCPbrufIc71F/EZjauFZ+tTrbWxT8jwOL1c07TbfS5C8pGdLVvi/1B1hrT3 TlVO8NqjvS9+v3h6ishu66JnyXztv+bI6Y58ZOkc3a5rzebikdXI/vb8DI7vGdNKpXCt Amw0wSSzQeaD/QCSvDj8Vg25aLhC/LyNXHejp/I+yPD1GJiGwlib8emUQuLEdbtKfQlE A9gUqcg/wQsRsc+jOktaZLG60FSFNiC2snwMIkwTLiorQjl3qt20GQD9Ts+Q0ogeqWqR ONNaC4/uo22ylgtmVrXl7YMtD27zO2nMdE/MstBX0Ad83KjPWTxinF1tnt7rhHSLO7XL cbXg== 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=B4X15ZN/wgvehnQbMInx5u21dSpO/o/y6oKeSSXY7i4=; b=ZofsDvniZY3+Ly302yVDfRian5aGUzLEVbRQ9OICUTQOXx2wOq13CYOrFucymRtR79 6cShYIxkm0dUWKbh4+tzEW7VcFpDP34RG2XHGpf26SkUeGOGp27BM6OvEJ0JLau/VLzU kwHKzf17Air2uADZ347nyq9Tcmdtp/8dzOylY9ldG9y3UpJnnzf8tvYqftsTgfYGTxQJ gteD3PUL+9OsF6Vgxo5qZ8MFTr3TXYcjdp4fozZXE5MmWZl1NcS8s4+87PYJuhIetV5/ 7ZIL1taKYXYeAooewstqObZI7YO7vkhAuztfXzD13z9bMdIt8TvuRcFZ38TdAcU6Srra WgqQ== X-Gm-Message-State: AOAM5330q3Tm2JZ2IR88njs067f3foztUNv2cJIZXYUr9lHsc2BEQMLx VKSPjY+jd2qkXn9lq506g7wL3b6Wt9w= X-Google-Smtp-Source: ABdhPJzZH63FiWHIJ00sXSgkSMDOOcw+pE8rVTuc/TBV6lcwel0rbdcX+dreZB89MTqJmksoxd5K0g== X-Received: by 2002:ac8:dd:: with SMTP id d29mr7948743qtg.392.1590408930556; Mon, 25 May 2020 05:15:30 -0700 (PDT) Original-Received: from minid (cbl-45-2-119-47.yyz.frontiernetworks.ca. [45.2.119.47]) by smtp.gmail.com with ESMTPSA id i24sm15047804qtm.85.2020.05.25.05.15.29 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Mon, 25 May 2020 05:15:29 -0700 (PDT) In-Reply-To: (chiaki-ishikawa-thunderbird-account's message of "Wed, 20 May 2020 13:31:29 +0900") 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:180966 Archived-At: chiaki-ishikawa-thunderbird-account writes: > Short of lisp function, maybe I can add message print out in alloc.c > to print out such information so that it gets recorded in *Message* > buffer. > It is done only when gabage-collection-message is t and there should > be some throttling mechanism to avoid spamming the user. > Any pointer re the hook(s) short of rewriting alloc.c is > appreciated. Well, if worst comes to worst, I don't mind rewriting > alloc.c to create an array of fixed size to store the last dozen or so > GC-related information that is updated before and after invocation of > a certain GC entry point. > I can print that out after a long GC to learn the memory situation. > But that sounds a bit drastic. OTOH, it may be the only way to go. That should probably work. I see the current garbage_collection_messages code uses message_nolog, I guess because growing the *Messages* buffer could also trigger GC.