Re: [scratch/igc] 985247b6bee crash on Linux, KDE, Wayland

[Eli Zaretskii]

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: execvy@gmail.com,  pipcet@protonmail.com,  emacs-devel@gnu.org
> Date: Thu, 05 Sep 2024 15:57:50 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> That means FRAME_OUTPUT_DATA can be null during the lifetime of a
> >> frame. If that happens, we'll crash exactly in that way in the new code
> >> for window frames.
> >
> > We never test for FRAME_OUTPUT_DATA being non-NULL in the code, so I
> > don't think I understand why igc.c is different.
> 
> Our scan functions can run at arbitrary times, including when
> FRAME_OUTPUT_DATA is still null.

OK, but if you look at the backtrace, you will see that in this case
the scan functions were run from within code called by
redisplay_internal, so I very much doubt that FRAME_OUTPUT_DATA was
NULL in this case.