Actually, I think you're right – it's probably not emacs.

I was trying out a fancy new Wayland-based window manager (sway) when this happened. Switched back to its X-based ancestor (i3) and have been fine for at least a week.

Feel free to close the bug report, thanks for your time.

Lars Ingebrigtsen <larsi@gnus.org> writes:

Charles Godfrey <cgodfrey@uw.edu> writes:

I've gotten several crashes this week. The latest happened while using mu4e and trying to open an html email in firefox. I've started to strongly suspect something is going weird with firefox + emacs, as they crashed simultaneously. It also looks like something's up with the X server?? Here is the output of bt-full:

Could you resend the output in a non-HTML message? The output was pretty much unreadable here. But if Firefox is also crashing, it doesn't sound very likely that this is an Emacs problem. RAM problem or something?

–