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#54698: non-recursive GC marking [PATCH] Date: Wed, 06 Apr 2022 13:59:08 +0300 Message-ID: <83r16acwar.fsf@gnu.org> References: <5A577100-75CE-4C9E-A7DA-02B917662AF5@acm.org> <8735itglid.fsf@gnus.org> <8527E407-8190-4574-B8D5-BE68220AE663@acm.org> <871qyc5o0y.fsf@yahoo.com> <5BBEDBDA-4C85-4237-9EF7-5635A4950365@acm.org> <83fsmreox8.fsf@gnu.org> <83a6czekro.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37355"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, mattiase@acm.org, p.stephani2@gmail.com, 54698@debbugs.gnu.org, larsi@gnus.org To: rms@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Apr 06 13:00:12 2022 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 1nc3OW-0009Yq-Kx for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 06 Apr 2022 13:00:12 +0200 Original-Received: from localhost ([::1]:47352 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nc3OV-00089I-BP for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 06 Apr 2022 07:00:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33746) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nc3OM-000898-Rm for bug-gnu-emacs@gnu.org; Wed, 06 Apr 2022 07:00:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34978) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nc3OM-00044s-Hh for bug-gnu-emacs@gnu.org; Wed, 06 Apr 2022 07:00:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nc3OM-0001mO-Ek for bug-gnu-emacs@gnu.org; Wed, 06 Apr 2022 07:00:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 06 Apr 2022 11:00:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 54698 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 54698-submit@debbugs.gnu.org id=B54698.16492427576750 (code B ref 54698); Wed, 06 Apr 2022 11:00:02 +0000 Original-Received: (at 54698) by debbugs.gnu.org; 6 Apr 2022 10:59:17 +0000 Original-Received: from localhost ([127.0.0.1]:57108 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nc3Nc-0001kn-Pg for submit@debbugs.gnu.org; Wed, 06 Apr 2022 06:59:17 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:40358) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nc3Nb-0001kX-4q for 54698@debbugs.gnu.org; Wed, 06 Apr 2022 06:59:15 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:53880) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nc3NV-0003z9-He; Wed, 06 Apr 2022 06:59:09 -0400 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=MtDJH4Zu/1GLD4c0lcwzslVZiAf+KITUk43I7xW2SJU=; b=IzzeXQUWNuLp CLJtff/bbibpNNfe4YuczM20SCqsoD6Ns7yinNrmE0nM/VGcWNEXGWrUPwwg2Ed68FuV5WTptG3JA ONi43FEh3JiszVgh7dUL0+mPo8txGOXV6LyewndlnhTWofuOndFIvFX5z15QUSk/tvg5YF3t3grtB CXGwHBtBCDDwPg2YWcrtJ4Ryc+nCk4s2Cw1EFJP/M/FC9PT0EqPLGTrs78adX1QvVxKRTfBXcTjnz 77qro+df04+elX2t1Jjo67HrzFt5WobZ41nB16Vd2TU+VWL6mF1DBHrpAM1HJuS316zBXjUPkppj5 HMUkmN57wEHpYAA7HEvyZg==; Original-Received: from [87.69.77.57] (port=3860 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nc3NN-0003KL-Nn; Wed, 06 Apr 2022 06:59:05 -0400 In-Reply-To: (message from Richard Stallman on Wed, 06 Apr 2022 00:09:25 -0400) 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:229486 Archived-At: > From: Richard Stallman > Cc: p.stephani2@gmail.com, luangruo@yahoo.com, mattiase@acm.org, > larsi@gnus.org, 54698@debbugs.gnu.org > Date: Wed, 06 Apr 2022 00:09:25 -0400 > > > > I think this is just how modern OSes behave: they will happily hand > > > out arbitrary amounts of memory and then kill processes without > > > warning if they use too much memory. By design, there's nothing these > > > processes can do about that. > > > That's not my experience. > > A few weeks ago, when I had too little physical memory for a while, > I found that my machine would start thrashing, and then Linux would > kill a large process. Fortunately that was IceCat, not Emacs. > A wizard told me it was indeed killing processes without warning, > but at that moment the thrashing process had no way to receive or > act on a warning. You seem to be saying that Emacs on GNU/Linux cannot reliably detect that it's approaching the memory limit, or have already approached it. That'd be sad if it were indeed 100% true, and couldn't be alleviated by some system setting. (I thought one could use "ulimit -v"?) Or maybe Emacs should have its own setting for how much memory is available, if it can reliably tell how much is being used. If indeed this cannot be solved on GNU/Linux, it is IMO sad, because on MS-Windows I was saved several times by memory_full and what's behind it, when I occasionally needed to visit very large files that exceeded my system's capacity for Emacs.