docker-firefox icon indicating copy to clipboard operation
docker-firefox copied to clipboard

v1.12.0 seems to be crashing all the time

Open jrdoublet opened this issue 4 years ago • 7 comments

Hi, I run 2 firefox containers, one with v1.11.0 and one with v1.12.0 my docker compose files are exactly the same except the version

v1.12 crashes all the time v1.11 is fine

here's my docker compose file :

Firefox - Web Browser

firefox-vpn: image: jlesage/firefox:v1.11.0

image: jlesage/firefox:latest

container_name: firefox
restart: unless-stopped
network: traefik
security_opt:
  - no-new-privileges:true
volumes:
  - $USERDIR/docker/firefox:/config
  - /dev/shm:/dev/shm
  - $USERDIR/shared_data:/shared
environment:
  USER_ID: $PUID
  GROUP_ID: $PGID
  TZ: $TZ
  UMASK: 002
  KEEP_APP_RUNNING: 1
  CLEAN_TMP_DIR: 1
  DISPLAY_WIDTH: 1600
  DISPLAY_HEIGHT: 960
  VNC_PASSWD: $FIREFOX_VNC_PASSWD
labels:
  - "traefik.enable=true"
  ## traefik conf....

jrdoublet avatar Jun 25 '20 21:06 jrdoublet

What do you mean exactly by "is crashing"? Firefox doesn't start ? Could you provide the container's log ?

jlesage avatar Jun 25 '20 23:06 jlesage

My is crashed as well. image

alexsahka avatar Jun 26 '20 01:06 alexsahka

@alexsahka, you seem to have a different issue. Did you set the --shm-size parameter ? https://github.com/jlesage/docker-firefox#increasing-shared-memory-size

jlesage avatar Jun 28 '20 23:06 jlesage

I am also seeing this in the latest, my tabs keep randomly crashing. I also already had the --shm-size 2g. I am running the Docker container on my unraid. v1.11 worked perfectly fine.

M1K3Yio avatar Jun 29 '20 14:06 M1K3Yio

I'm sorry, I couldn't find the logs, could you please help me ?

I've retrieve these logs, but they're useless :

30/06/2020 10:27:50 periodic repaints., 30/06/2020 10:27:50 GrabServer control via XTEST., 30/06/2020 10:27:50 , 30/06/2020 10:27:50 Scroll Detection: -scrollcopyrect mode is in effect to, 30/06/2020 10:27:50 use RECORD extension to try to detect scrolling windows, 30/06/2020 10:27:50 (induced by either user keystroke or mouse input)., 30/06/2020 10:27:50 If this yields undesired behavior (poor response, painting, 30/06/2020 10:27:50 errors, etc) it may be disabled via: '-noscr', 30/06/2020 10:27:50 Also see the -help entry for tuning parameters., 30/06/2020 10:27:50 You can press 3 Alt_L's (Left "Alt" key) in a row to , 30/06/2020 10:27:50 repaint the screen, also see the -fixscreen option for, 30/06/2020 10:27:50 periodic repaints., 30/06/2020 10:27:50 , 30/06/2020 10:27:50 XKEYBOARD: number of keysyms per keycode 7 is greater, 30/06/2020 10:27:50 than 4 and 51 keysyms are mapped above 4., 30/06/2020 10:27:50 Automatically switching to -xkb mode., 30/06/2020 10:27:50 If this makes the key mapping worse you can, 30/06/2020 10:27:50 disable it with the "-noxkb" option., 30/06/2020 10:27:50 Also, remember "-remap DEAD" for accenting characters., 30/06/2020 10:27:50 , 30/06/2020 10:27:50 X FBPM extension not supported., Xlib: extension "DPMS" missing on display ":0"., 30/06/2020 10:27:50 X display is not capable of DPMS., 30/06/2020 10:27:50 --------------------------------------------------------, 30/06/2020 10:27:50 , 30/06/2020 10:27:50 Default visual ID: 0x21, 30/06/2020 10:27:50 Read initial data from X display into framebuffer., 30/06/2020 10:27:50 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/6400, 30/06/2020 10:27:50 , 30/06/2020 10:27:50 X display :0 is 32bpp depth=24 true color, 30/06/2020 10:27:50 , 30/06/2020 10:27:50 Listening for VNC connections on TCP port 5900, 30/06/2020 10:27:50 , 30/06/2020 10:27:50 Xinerama is present and active (e.g. multi-head)., 30/06/2020 10:27:50 Xinerama: number of sub-screens: 1, 30/06/2020 10:27:50 Xinerama: no blackouts needed (only one sub-screen), 30/06/2020 10:27:50 , 30/06/2020 10:27:50 fb read rate: 86 MB/sec, 30/06/2020 10:27:50 fast read: reset -wait ms to: 10, 30/06/2020 10:27:50 fast read: reset -defer ms to: 10, 30/06/2020 10:27:50 The X server says there are 10 mouse buttons., 30/06/2020 10:27:50 screen setup finished., 30/06/2020 10:27:50 , , The VNC desktop is: c9331b8b82ea:0,, 0, , ******************************************************************************, Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?, , The scheme stores pixel data offscreen on the VNC viewer side for faster, retrieval. It should work with any VNC viewer. Try it by running:, , x11vnc -ncache 10 ..., , One can also add -ncache_cr for smooth 'copyrect' window motion., More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching, , [services.d] starting logmonitor..., [services.d] starting certsmonitor..., [certsmonitor] disabling service: secure connection not enabled., [logmonitor] starting..., [services.d] starting nginx..., [services.d] starting statusmonitor..., [nginx] starting..., [services.d] starting app..., [app] starting Firefox..., [statusmonitor] starting..., [services.d] done., Mozilla Firefox 77.0.1, 30/06/2020 11:19:22 Got connection from client 127.0.0.1, 30/06/2020 11:19:22 other clients:, 30/06/2020 11:19:22 Got 'ws' WebSockets handshake, 30/06/2020 11:19:22 Got protocol: binary, 30/06/2020 11:19:22 - webSocketsHandshake: using binary/raw encoding, 30/06/2020 11:19:22 - WebSockets client version hybi-13, 30/06/2020 11:19:22 Disabled X server key autorepeat., 30/06/2020 11:19:22 to force back on run: 'xset r on' (3 times), 30/06/2020 11:19:22 incr accepted_client=1 for 127.0.0.1:35566 sock=10, 30/06/2020 11:19:22 Client Protocol Version 3.8, 30/06/2020 11:19:22 Protocol version sent 3.8, using 3.8, 30/06/2020 11:19:22 rfbProcessClientSecurityType: executing handler for type 1, 30/06/2020 11:19:22 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8, 30/06/2020 11:19:22 Pixel format for client 127.0.0.1:, 30/06/2020 11:19:22 32 bpp, depth 24, little endian, 30/06/2020 11:19:22 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0, 30/06/2020 11:19:22 no translation needed, 30/06/2020 11:19:22 Enabling NewFBSize protocol extension for client 127.0.0.1, 30/06/2020 11:19:22 Enabling full-color cursor updates for client 127.0.0.1, 30/06/2020 11:19:22 Using image quality level 6 for client 127.0.0.1, 30/06/2020 11:19:22 Using JPEG subsampling 0, Q79 for client 127.0.0.1, 30/06/2020 11:19:22 Using compression level 9 for client 127.0.0.1, 30/06/2020 11:19:22 Enabling LastRect protocol extension for client 127.0.0.1, 30/06/2020 11:19:22 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECC), 30/06/2020 11:19:22 Using tight encoding for client 127.0.0.1, 30/06/2020 11:19:22 client_set_net: 127.0.0.1 0.0000, 30/06/2020 11:19:22 created xdamage object: 0x200036, 30/06/2020 11:19:22 copy_tiles: allocating first_line at size 51, 30/06/2020 11:19:32 created selwin: 0x200037, 30/06/2020 11:19:32 called initialize_xfixes(),

jrdoublet avatar Jun 30 '20 09:06 jrdoublet

ok I think I found the logs

I've seen two errors :

  • 1st one in nginx/error.log : Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Failed buffer for 0, 0, 1600, 885 (t=233447) [GFX1-]: Failed buffer for 0, 0, 1600, 885

  • 2nd one in firefox/error.log :

###!!! [Parent][MessageChannel] Error: (msgtype=0x380035,name=PContent::Msg_UpdateSharedData) Channel error: cannot send/recv

[Parent 6237, Main Thread] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /home/buildozer/aports/community/firefox/src/firefox-77.0.1/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc, line 19 [Parent 6237, Gecko_IOThread] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /home/buildozer/aports/community/firefox/src/firefox-77.0.1/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc, line 19 [Parent 6237, Gecko_IOThread] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /home/buildozer/aports/community/firefox/src/firefox-77.0.1/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc, line 19 Gdk-Message: 10:12:44.953: firefox: Fatal IO error 0 (No error information) on X server :0.

I hope this helps

jrdoublet avatar Jun 30 '20 09:06 jrdoublet

The tab crash seems related to a system call not allowed by default by Docker. This particular system call (membarrier) will be whitelisted in the next Docker version.

For now, a quick workaround is to create the container with the following option:

--security-opt seccomp=unconfined

I will provide more details on the issue and the possible workarounds in the documentation.

jlesage avatar Jul 01 '20 15:07 jlesage