[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Failing to GC killed buffers considered harmful
From: |
Eli Zaretskii |
Subject: |
Re: Failing to GC killed buffers considered harmful |
Date: |
Sun, 29 Mar 2020 21:48:56 +0300 |
> From: Pip Cet <address@hidden>
> Date: Sun, 29 Mar 2020 16:46:03 +0000
> Cc: Daniel Colascione <address@hidden>, address@hidden
>
> > We could, of course, remove the assertion, but then we are left with a
> > dead buffer that will never be GC'ed, AFAIU, because objects that come
> > from the portable dump are considered constantly marked.
>
> The same is true of all other objects, though, right?
You mean, that they are considered marked? Yes.
> It seems like it's simply a bad assert to me.
Which one?
> The problem appears to be that "all_buffers" points to a killed
> buffer, and is remembered by pdumper.
Yes, because pdumper dumps all the Lisp objects present at that point,
after performing GC. What else can it do?
- Failing to GC killed buffers considered harmful, Eli Zaretskii, 2020/03/29
- Re: Failing to GC killed buffers considered harmful, Pip Cet, 2020/03/29
- Re: Failing to GC killed buffers considered harmful,
Eli Zaretskii <=
- Re: Failing to GC killed buffers considered harmful, Pip Cet, 2020/03/29
- Re: Failing to GC killed buffers considered harmful, Daniel Colascione, 2020/03/29
- Re: Failing to GC killed buffers considered harmful, Pip Cet, 2020/03/29
- Re: Failing to GC killed buffers considered harmful, Eli Zaretskii, 2020/03/29
- Re: Failing to GC killed buffers considered harmful, Pip Cet, 2020/03/30
- Re: Failing to GC killed buffers considered harmful, dancol, 2020/03/30
- Re: Failing to GC killed buffers considered harmful, Stefan Monnier, 2020/03/30
Re: Failing to GC killed buffers considered harmful, Stefan Monnier, 2020/03/30