GNU bug report logs - #54698
non-recursive GC marking [PATCH]

Previous Next

Full log

Message #85 received at 54698 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Po Lu <luangruo <at> yahoo.com>
Cc: larsi <at> gnus.org, mattiase <at> acm.org, p.stephani2 <at> gmail.com,
 54698 <at> debbugs.gnu.org, rms <at> gnu.org
Subject: Re: bug#54698: non-recursive GC marking [PATCH]
Date: Wed, 06 Apr 2022 15:23:20 +0300

> From: Po Lu <luangruo <at> yahoo.com>
> Cc: rms <at> gnu.org,  p.stephani2 <at> gmail.com,  mattiase <at> acm.org,  larsi <at> gnus.org,
>   54698 <at> debbugs.gnu.org
> Date: Wed, 06 Apr 2022 20:05:14 +0800
> 
> Overcommit can be disabled on GNU/Linux (the relevant knob is
> vm.overcommit_memory), which will malloc return an error when there is
> no more memory left on the system, thereby triggering memory_full.

Then I think we should advise users to do that.

> malloc can also fail when it runs out of virtual memory, especially on
> 32-bit systems.

Why only 32-bit?  If overcommit is disabled, isn't the amount of VM
determined by the sum of physical memory + swap space?  If so, you
could run out of VM on 64-bit systems as well, no?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.