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: Fri, 21 Feb 2020 12:27:26 -0500 Message-ID: <85r1ynam0x.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="17578"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (windows-nt) 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 Fri Feb 21 18:28:12 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 1j5C60-0004Ok-AB for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 21 Feb 2020 18:28:12 +0100 Original-Received: from localhost ([::1]:34048 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j5C5z-00057b-9F for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 21 Feb 2020 12:28:11 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37515) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j5C5s-00056x-4s for bug-gnu-emacs@gnu.org; Fri, 21 Feb 2020 12:28:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j5C5r-0006h5-2v for bug-gnu-emacs@gnu.org; Fri, 21 Feb 2020 12:28:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42056) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j5C5q-0006gb-VR for bug-gnu-emacs@gnu.org; Fri, 21 Feb 2020 12:28:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1j5C5q-0002Ir-SR for bug-gnu-emacs@gnu.org; Fri, 21 Feb 2020 12:28:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Noam Postavsky Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 21 Feb 2020 17:28:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 39413 X-GNU-PR-Package: emacs Original-Received: via spool by 39413-submit@debbugs.gnu.org id=B39413.15823060558804 (code B ref 39413); Fri, 21 Feb 2020 17:28:02 +0000 Original-Received: (at 39413) by debbugs.gnu.org; 21 Feb 2020 17:27:35 +0000 Original-Received: from localhost ([127.0.0.1]:48026 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1j5C5O-0002Hq-Ui for submit@debbugs.gnu.org; Fri, 21 Feb 2020 12:27:35 -0500 Original-Received: from mail-qk1-f173.google.com ([209.85.222.173]:33934) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1j5C5M-0002HG-Cn; Fri, 21 Feb 2020 12:27:33 -0500 Original-Received: by mail-qk1-f173.google.com with SMTP id c20so2548627qkm.1; Fri, 21 Feb 2020 09:27:32 -0800 (PST) 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=x59Qasl8a1fYpAlioxMJcQ/XSOi0YIbJtmDOybdw5/A=; b=Yu3oPKVK9O7VUdJztcaWuEmWhmJ7ott4/RkpN32fUpfM13y5nFbz9+v0fLMPzDvhmk zGZ2/iV27kf2UeRqs8IwdE875P0zIQqxWGnUN/KObUozrGtUM+YwAv09eRYJ/1dClBb8 glKhlijSWLkALe2lgVckPBWKi57QcMtn5AcCKK4nLXGre/GoxR68pSzynywf7DnYSmVn elCFR103CXUqJFar7j857211AU7WGL0KeYyrlCV67c47PqvbjrxU2YNbaX0VrAJhiUzf QLgOjVvO9gQ5YdhmSzNVe+uOmIN4GLIGGoCnO1fnlx3M8JqcDZ+bxkHHbPAn9Cn0U/39 ycwQ== 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=x59Qasl8a1fYpAlioxMJcQ/XSOi0YIbJtmDOybdw5/A=; b=d3thQJJMp7W2uZxOTWZY8RyhnLQdE9LBUZtzNnabXStEmoWnBWq2r1UUyTuug8Iiqy Eg3pFRhZ/p14osBYbfLaPM+voqTB5Z//5AWajLntHveF46/LugX+LM2C+LgBr+IkuHeo 9M20HFpcTU6eHMzScm9qcLg1W7vEwVw9X/n3ZaPDNsvx71OTEr/lCzOSHUpdPeDlcX2Z Eh04h8XjftYfsHLFJ7Kfwlis/7OTPtbTuSSYlwlDmcvzuSkIqlyZnDJoJ1Vv4OsYKucW Prj1sA23w5cTRbKgxmBXWiR+9lLnUreyscacDTJv/VYmoYso/illAWVRGuKIuWz48zYo /iSQ== X-Gm-Message-State: APjAAAVV2oYwjqID6rEfGsnTybTp0eFpOTu1CI27o5wIG0qg1e10KU14 hxTY42h9clySEZnTn3qX5n5gjIUZfkU= X-Google-Smtp-Source: APXvYqyXA3jfqP1B+lePBA5N5QiJsAkgo+v67zUMry/kWaBmE7A4RKIR7zAXpX7PNh+nZZrKUvTb1w== X-Received: by 2002:a05:620a:42:: with SMTP id t2mr4565980qkt.45.1582306046722; Fri, 21 Feb 2020 09:27:26 -0800 (PST) Original-Received: from vhost2 (CPE001143542e1f-CMf81d0f809fa0.cpe.net.cable.rogers.com. [99.230.38.42]) by smtp.gmail.com with ESMTPSA id 132sm1814819qkn.109.2020.02.21.09.27.25 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 21 Feb 2020 09:27:26 -0800 (PST) In-Reply-To: (chiaki-ishikawa-thunderbird-account's message of "Tue, 4 Feb 2020 18:32:30 +0900") 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:176368 Archived-At: tags 39413 + unreproducible quit chiaki-ishikawa-thunderbird-account writes: > I printed stack backtrace and Emacs seemed to be in memory allocator. > Then I let it continue. > Still the emacs screen was locked up. > So I interrupted the execution, and printed stack backtrace. > Again Emacs was in memory allocator. > Eventually I gave up and killed emacs. > > It seems that garbage collection or > routine in alloc.c was looping. That's not enough evidence to show that the garbage collection was looping. There could be some higher level loop that does a lot of allocation, so that if you stop at some random point you would have a high probability of stopping in the alloc.c. If you catch this in gdb again, try running the 'finish' a few times to see if it can leave the alloc.c code. > This is not a repeatable bug. I have no idea how to reproduce this. It > occurs every now and then.