Bugzilla

(In reply to Olivier Tilloy from comment #37)
> In light of this last comment, I'm suspecting this might indeed be caused by the firefox snap (or the gnome platform snap which it depends on) being refreshed while it's running. There is work ongoing to prevent this, and an experimental feature already allows this, but it's not enabled by default, see https://forum.snapcraft.io/t/wip-refresh-app-awareness/10736 for details.
> 
> To everyone affected, next time you hit a similar crash, can you share the output of `snap changes` to confirm that the crash happened shortly after either the firefox snap or the gnome-3-38-2004 snap were updated?
> 
> And as a workaround until this is properly fixed in snapd, I strongly suggest turning on the experimental feature:
> 
>     snap set core experimental.refresh-app-awareness=true

I got the crash in a VM a few minutes ago, and `snap changes` does mention `firefox` as well as `gnome-3-38-2004`

(In reply to Olivier Tilloy from comment #37)
> In light of this last comment, I'm suspecting this might indeed be caused by the firefox snap (or the gnome platform snap which it depends on) being refreshed while it's running. There is work ongoing to prevent this, and an experimental feature already allows this, but it's not enabled by default, see https://forum.snapcraft.io/t/wip-refresh-app-awareness/10736 for details.
> 
> To everyone affected, next time you hit a similar crash, can you share the output of `snap changes` to confirm that the crash happened shortly after either the firefox snap or the gnome-3-38-2004 snap were updated?
> 
> And as a workaround until this is properly fixed in snapd, I strongly suggest turning on the experimental feature:
> 
>     snap set core experimental.refresh-app-awareness=true

I got the crash in a VM a few minutes ago, and `snap changes` does mention `firefox` as well as `gnome-3-38-2004`

I think the worst is that it's crashing the main process, and so we can't show `about:restartrequired`.