Bugzilla

(In reply to guest271314 from comment #16)
> (In reply to Nico Grunbaum [:ng] from comment #15)
> > Thanks for the info.
> > 
> > The previous bug was fixed by dispatching an X11 call to a different thread to avoid a deadlock in X11. IIRC the deadlock was caused by a bug in the X11 library that we use, but I would have to go back and do some more digging to say with confidence.
> > 
> > Just to be sure, you did try `CTRL` + `ALT` + `F3` (or greater), and the Capslock/Numlock don't work?
> > This article[0] mentions some methods to try to recover from an X crash.
> > * You can try pressing `CTRL` + `SYSREQ` + `r` which will take keyboard control away from X, then try `CTRL` + `ALT` + `F(#)`.  
> > * `CTRL` + `SYSREQ` + `k` will kill all the programs you have running on a virtual console, including your X server.
> > 
> > [0]  https://www.howtogeek.com/119293/4-ways-to-recover-from-a-crashed-or-frozen-x-server-on-linux/
> 
> From recollection tried to get to  a shell prompt using ```CTRL ALT F2```. The OS was unresponsive. When try again at Firefox will confirm. Even if a shell prompt is possible the result of calling getDisplayMedia() is still a bug. What should the user do at ```terminal``` besides kill Firefox and try to regain control of the system? Users that are familiar with terminal are not expecting JavaScript code run at the browser to freeze the OS.

(In reply to guest271314 from comment #16)
> From recollection tried to get to  a shell prompt using ```CTRL ALT F2```. The OS was unresponsive. When try again at Firefox will confirm. Even if a shell prompt is possible the result of calling getDisplayMedia() is still a bug. What should the user do at ```terminal``` besides kill Firefox and try to regain control of the system? Users that are familiar with terminal are not expecting JavaScript code run at the browser to freeze the OS.

Sure, I am not proposing this as a solution. I am trying to determine if the behavior of the bug is the same as the bug mentioned above. That bug would lock up X, but otherwise leave the system running. One could get to the terminal and kill Firefox and then the desktop would unlock.

Thanks for your help so far.