GNU bug report logs - #76406
31.0.50; Crash with tty child frames

Previous Next

Full log

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

From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: rudalics <at> gmx.at, 76406 <at> debbugs.gnu.org
Subject: Re: bug#76406: 31.0.50; Crash with tty child frames
Date: Thu, 20 Feb 2025 18:22:25 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Cc: 76406 <at> debbugs.gnu.org
>> From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
>> Date: Thu, 20 Feb 2025 15:21:04 +0100
>> 
>> The root frame ended up containing glyphs from a dead menu frame. The
>> dead frame's face cache was set to NULL because it had been freed. The
>> series of events leading to this is still unclear to me. At least we
>> never copy glyphs from a dead frame, that much I can say.
>
> Should deleting a frame on a TTY make sure there are no glyphs in the
> root frame's current glyph matrix whose frame pointer refers to the
> frame being deleted?

It should. Deleting a child frame should ensure that its root is redrawn
thoroughly, for the long longer existing child. Which would include
clearing the root's current matrix. Why that doesn't happen is unclear
to me.

Previous Next

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