GitLab

2017/10/24 04:34:29 firefox: firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
2017/10/24 04:34:29 firefox:
2017/10/24 04:34:29 firefox: [Child 50] ###!!! ABORT: Aborting on channel error.: file /home/debian/build/tor-browser/ipc/glue/MessageChannel.cpp, line 2152
2017/10/24 04:34:29 firefox: [Child 50] ###!!! ABORT: Aborting on channel error.: file /home/debian/build/tor-browser/ipc/glue/MessageChannel.cpp, line 2152
2017/10/24 04:34:29 tor: Oct 24 08:34:29.000 [notice] Catching signal TERM, exiting cleanly.
2017/10/24 04:34:29 failed to accept control conn: accept unix /run/user/1000/sandboxed-tor-browser/control: use of closed network connection
2017/10/24 04:34:29 failed to accept SOCKS conn: accept unix /run/user/1000/sandboxed-tor-browser/socks: use of closed network connection

I assume the X11 surrogate falls behind when doing things that are extremely graphically intensive on anemic hardware or something, but that's just a hypothesis since I don't have reproduction instructions.

I'm not going to remove the surrogate since filtering extensions is a more reliable way to fix the MIT-SHM related crashes that hooking the X libraries never completely solved.