From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#69263: 29.1; emacs freeze with memory swap Date: Mon, 19 Feb 2024 14:41:58 +0200 Message-ID: <86wmr0pqw9.fsf@gnu.org> References: Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31387"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 69263@debbugs.gnu.org To: awrhygty@outlook.com Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Feb 19 13:42:58 2024 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 1rc2z2-0007zH-QE for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 19 Feb 2024 13:42:56 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rc2yp-00056n-E2; Mon, 19 Feb 2024 07:42:43 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rc2yn-00056Q-Du for bug-gnu-emacs@gnu.org; Mon, 19 Feb 2024 07:42:41 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rc2yn-0006Ct-59 for bug-gnu-emacs@gnu.org; Mon, 19 Feb 2024 07:42:41 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rc2z7-0001Tf-QF for bug-gnu-emacs@gnu.org; Mon, 19 Feb 2024 07:43:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 19 Feb 2024 12:43:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 69263 X-GNU-PR-Package: emacs Original-Received: via spool by 69263-submit@debbugs.gnu.org id=B69263.17083465505636 (code B ref 69263); Mon, 19 Feb 2024 12:43:01 +0000 Original-Received: (at 69263) by debbugs.gnu.org; 19 Feb 2024 12:42:30 +0000 Original-Received: from localhost ([127.0.0.1]:40604 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rc2yb-0001So-Gl for submit@debbugs.gnu.org; Mon, 19 Feb 2024 07:42:29 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:52020) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rc2yZ-0001SY-F8; Mon, 19 Feb 2024 07:42:28 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rc2y8-000652-Sl; Mon, 19 Feb 2024 07:42:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=rLwYYcDYm5F/6CKDYFZ2izHkp+od1GXAMlmjkHbtOqY=; b=iiqpUX9Hfw8F niB2p8Hy/AU/wcUffIUaWwia/0/fXSTJWDRByKPtuRCiVgZyrhX2JTqRQg2rPakvownrz5DtSm75N JRxVqXBVvqwxfQ7bRfo+mpeHd+tnHC63GfbohXG/9WJQo7gnS0Ay93NF4rZ2+umqbPRE3/922wLlU kPHjQ78jZPVbGg+dfyBrzOWHEZQGGlxu9OJDIbDMaAsnEH+2RaNysIkuNiUrRSYAqxZPliIRga3k4 CI+ZhOaz452RWAr2kt4SYj1EqTzTUK6Gr5h5vlvH9B/2dgCzrSJK3t+vItgjo7MotuA5UDJZhUJHd rB4C8SfzkWqbG13x3frrnQ==; In-Reply-To: (awrhygty@outlook.com) 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:280257 Archived-At: tags 69263 moreinfo thanks > From: awrhygty@outlook.com > Date: Mon, 19 Feb 2024 14:56:10 +0900 > > > My PC has 8GB memory and HDD, no SSD. > Emacs freezes with the procedure below. > > (0) Close all applications. > (1) Start task manager. > Confirm disk usage is low and memory usage is about 2GB or less. > (2) Start emacs -Q > (3) Evaluate the form below > (progn (make-string (* 8000 1000 1000) 0) > (kill-emacs)) > (4) Memory usage increases and then decreases in ten seconds. > (5) Disk usage keep 100% active for a few minutes. > (6) Application window of emacs keep alive and emacs process name is > displayed in the process tab of task manager. > (At least 10 hours, I waited.) I don't have a 8GB 64-bit Windows system to try this, and the results are likely to be dependent on the intimate details of the Virtual Memory setup on that system. So if you want to help us understand what happens in the strange case where a Lisp program creates a 8GB Lisp string, and clear it all, on a 8GB MS-Windows system, please attach GDB to Emacs after running the above recipe, and produce a backtrace that can be used to try to figure out what happens. (I hope that your Emacs binary is not stripped of debugging symbols, because if it's stripped, GDB will not tell anything useful.) Thanks.