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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Philipp Stephani <p.stephani2 <at> gmail.com>
Cc: luangruo <at> yahoo.com, mattiase <at> acm.org, larsi <at> gnus.org, 54698 <at> debbugs.gnu.org
Subject: Re: bug#54698: non-recursive GC marking [PATCH]
Date: Tue, 05 Apr 2022 16:12:59 +0300

> From: Philipp Stephani <p.stephani2 <at> gmail.com>
> Date: Tue, 5 Apr 2022 14:31:17 +0200
> Cc: Mattias Engdegård <mattiase <at> acm.org>, 
> 	Po Lu <luangruo <at> yahoo.com>, Lars Ingebrigtsen <larsi <at> gnus.org>, 54698 <at> debbugs.gnu.org
> 
> > You mean, Emacs fails to know when it approaches the memory limit,
> > and/or react reasonably when memory_full is called?  That'd be a bug,
> > IMO.
> 
> 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.

Previous Next

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