From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#45200: [PATCH] Force Glibc to free the memory freed Date: Wed, 3 Feb 2021 08:39:48 +0100 Message-ID: <7ffacc5f-fc0e-a5f8-104d-2c0ae8e06953@gmx.at> References: <83k0rz21dw.fsf@gnu.org> <331805c74fc5d3d412dd2065030b11fa3343710d.camel@yandex.ru> <8a91fc16f93298bca1281b43d6821ae3621376dc.camel@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4835"; mail-complaints-to="usenet@ciao.gmane.io" Cc: carlos@redhat.com, fweimer@redhat.com, 45200@debbugs.gnu.org, dj@redhat.com To: Konstantin Kharlamov , Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Feb 03 08:41:32 2021 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 1l7Cn5-0001Au-UE for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 03 Feb 2021 08:41:31 +0100 Original-Received: from localhost ([::1]:50290 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l7Cn1-0001Fg-RW for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 03 Feb 2021 02:41:27 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33530) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l7Cmc-0001FF-Jg for bug-gnu-emacs@gnu.org; Wed, 03 Feb 2021 02:41:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53320) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1l7Cmc-0006v8-5U for bug-gnu-emacs@gnu.org; Wed, 03 Feb 2021 02:41:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1l7Cmc-00025q-2n for bug-gnu-emacs@gnu.org; Wed, 03 Feb 2021 02:41:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 03 Feb 2021 07:41:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 45200 X-GNU-PR-Package: emacs Original-Received: via spool by 45200-submit@debbugs.gnu.org id=B45200.16123380037946 (code B ref 45200); Wed, 03 Feb 2021 07:41:02 +0000 Original-Received: (at 45200) by debbugs.gnu.org; 3 Feb 2021 07:40:03 +0000 Original-Received: from localhost ([127.0.0.1]:36633 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1l7Cle-000244-M9 for submit@debbugs.gnu.org; Wed, 03 Feb 2021 02:40:02 -0500 Original-Received: from mout.gmx.net ([212.227.17.22]:33421) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1l7Clc-00023W-Qz for 45200@debbugs.gnu.org; Wed, 03 Feb 2021 02:40:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1612337990; bh=K5fejfNmO6xd3ohLKXviF/8V5lP8eMPnuR8jht7YxZw=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=FAvCx8biLwyAfba2ZHAIFJ7XzYn3I5IzOSXMgDcHUsbeyl5QfrxA4zBEbhHshJ8qJ 0hgYmqPAMJkMxvUVm1jPE7HfY0IvNKKyNYiPQqu/i5soN2RX+Ta10P897skN37SSlY C8vFdiNKQeNd9bUYuodfwRoz4HqPAumgxMuNPdCU= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.100] ([46.125.249.123]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MGz1f-1lBLNN1qct-00E7Fh; Wed, 03 Feb 2021 08:39:50 +0100 In-Reply-To: <8a91fc16f93298bca1281b43d6821ae3621376dc.camel@yandex.ru> Content-Language: en-US X-Provags-ID: V03:K1:jpYzOR6MmOWbH51cp+h1AgKIG5HcVLfPW30ikzHXB6epZOLLW+O ovrqBwzilRIRNxxwguWnSzvgtjIMoQ2wPd28Zr/TvFi+szui4N/LKvqsbszFsdCVkfCOlXQ wwEReFXv8qAWFfvl4A/8Dv4HhmIqXuoVc3fkEbc8XjZNUTxJo35+oWDkOSGdQ4nhm7SaGHy RrDZsqTvrOV3meTDsxNgQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:lR4ulWz6NWc=:5ITJoSbrKiJig8qkQQLiNs T4EueZdSBAJMySLrKIm6oZGbnSw4j7gLbCEJrV7zwBQKE5Thb1qZA4knZ8LVmR45/K60tH04K M6K7SQOwEkb6GKmVVJUHgEEzOl+tTIoMBfvWXijUpSN/j6vETeDS/fhumvaOHcIBU0ar01zVE frG8fNtbu4h3rsU0LfjAqKCZF+xu8AChq5OMh25/EqMAmk0fNZlwy8GGFyYh82SK940F3TqzZ 7XsBpD4wrOaDXxHNolQK1oiTRm7zYu6y46y+/35BxhTjpBaw9HHgsygx1S50WDENHPRo9YiZ/ RDXdciROL1CD4+jQyBrq6JXpGe1yHz94i0kR1tbh/hW7G9PvKPTcV5Hkt+HiaR//oxIYkGH4P EDtQYv60DXxpI8rZucmKy7hI6Wm+784yVStXXII3hFTI0RCmgGaf8C2WRUv21oNiKiWMDzg/w 9995P4lIRS+/YmS+JTAtoo67wF3Ktqh4v1L6klayGtOhgxv3cw9rXVFxSFHe1Q8SXNaBFApvt 5DkoRDy8GHaA7uzWmVRy32OcAUNyJ0qVYTs4HPUksBZlzduBSlZiaZN62BHEZaeMNCjRr4SlQ 8T+31QntBq3ilen2IbxJWOWHeZuMhJm56dgdkjU6PfU+gU6vmsh8LZvaUQUtZZ70yVfh2WBic KY0+16/LQi6tM90WDwYc5nOW31rOhZXtTInv+4oKtrVN778wET22IuzNWVS8nBUqwAy07K9jR gC7c8BqjktfkWPY8MQSAdXQpa9qxNdwKIbCOZl8M5x+nldWs4zlILn7zHBPxCP/4Ze+gaIXQ 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:199180 Archived-At: > Well, I didn't send the patches for my only benefit, but for benefit > of others people. The new ELisp function is something that not too > many people would benefit from, and I mean, including those who > disable GC. Does anyone really disable GC and get away with it? > That is because it would be an opt-in feature, which you > need to know about to enable it, and not many will ever find out about > it. I wouldn't be afraid of that. In the past months we had a sufficient number of candidates caring about the memory consumption of their Emacs sessions. An opt-out feature OTOH would get us soon a couple of people who decide that your feature is responsible for some new slowness and recommend to throw it out. So making this an opt-in feature and at the same time giving some recommendations of what users can do when they detect that their sessions consumes more memory than expected would be a finely balanced solution IMO. martin