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.
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.