Firefox

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1835682/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

Thank you for the report karah. Had this bug been reported before? If so, then there was no need to file a new bug, otherwise I'm not sure how you'd expect an unreported bug to be fixed.

Anyway, I'm able to observe the issue as you describe it in a 19.04 VM. Keeping the F11 key down seems to grind the shell to a halt, but I don't see it crash. Instead, it appears frozen, but if I release the F11 key and wait for a while, the system becomes usable again. Without further investigation, I guess what happens is that firefox queues a large number of (fullscreen on; fullscreen off) events while the F11 key is down, and the window manager needs some time to cope with these requests.

It's probably a firefox bug, but I'm adding a mutter task too, because presumably the window manager should be more resilient to faulty behaviours like that.

I’ve actually seen firefox crash in a 19.10 VM while testing this, but this didn't produce a crash file in /var/crash. gnome-shell's memory usage had climbed to 90%, and it was restored to a reasonable value after firefox crashed.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1749779, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Possibly related upstream bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=185194