Hi John,

All of your crash reports indicate that Firefox loses connection to Wayland (and, treating this as a fatal error, crashes). I believe we have bug 1890074 for this issue, but I'm not sure about its state. I suggest that you add your context to the bug and, if you want, try to ask the assignee if they have any tips.

You can also post any reply here to ensure the question remains discoverable for other contributors.

I have resolved the issue by removing Firefox and installing Firefox-esr (the extended support release). All the issues I was having appear resolved. My research suggests the issue was some kind of communication failure between Firefox’s native Wayland protocol and Sommelier, the bridging service that translates Linux graphics for the Chromebook display. For other users reference, I installed Firefox-esr using apt.

Great, thank you for sharing this!

It's been like almost a month already and this critical issue is still unsolved, I updated firefox and none of the minor updates of 147 even improved this, today I thought with 148 a solution would arrive, but nothing happened. Firefox 148 crashes extremely easily, the shortest path to a complete crash seems to press the hamburger menu 3 times, you can kinda avoid crashes if you limit click based interactions with the ui but it's still very likelyl you will face that even then. I'm also on chromebook crostini, everthing updated. Firefox stable from the official repository has this issue, also the flatpak version, also librewolf, zen browser, and as OP said, firefox esr is the only version that works as of today. Using MOZ_ENABLE_WAYLAND=0 firefox to force firefox stable to run using x11 works but is extremely buggy and slugish, when the right click menu is opened, it appears initially in the center of the screen and then teleports to the correct location, this also happens with the hamburguer menu. This is very far from a stable usable piece of software in its current state, my device is mid/low end so I really do notice the performance improvements that firefox stable receives, even firefox esr, I'm guessing will have the same issue when the next big update comes to it. I wish I could stay on firefox to support their indie web engine, but this is making me leave until a TRUE solution is presented.