On Sun, 2023-12-10 at 07:06 -0600, Roger Heflin wrote: > This is not an out of memory crash. > > This is a code bug in firefox and/or in the shared library being > called by firefox. > > Usually this is related to something unexpected/unhandled in the data > stream being processed incorrectly. > > I have had a few of these firefox crashes since around Nov 20. > > Hopefully someone fixes it soon. > I assumed it was an OOM since that's mostly what pops up on Google searches, but it may not be. What I neglected to point out was that when I turned on my monitor this morning the system was completely unresponsive, i.e. no mouse and no keyboard. The screen showed my (frozen) desktop session. The journal ended with the crash I reported, i.e. nothing happened after that including my usual backup and hibernation routines. I had to hard reset the system to get back in. It should not be possible for a userland process to cause this, which i why I thought it could be OOM. poc -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
