splash: The X11 connection broke (error 1). Did the X11 server die?
Hey, I’m currently using splash via Docker and I’m having my container “randomly” die with an exit code of 137. The only relevant message I can see in the log output is the last line:
The X11 connection broke (error 1). Did the X11 server die?
I’ve also seen this in the dimes output but I think it might be a separate condition:
python3[4064]: segfault at 14 ip 00007f6a449edf84 sp 00007ffd58796f70 error 4 in libQt5WebKit.so.5.5.1[7f6a440a5000+20a9000]
I’d say this happens after I have crawled a couple of hundred pages (it doesn’t seem to be anything specific about an individual page because it crashes randomly). Possibly something running out of memory? Curious if others have seen the same issue or have ideas how I might get more information to help debug.
About this issue
- Original URL
- State: open
- Created 8 years ago
- Comments: 15
This may just be coincidence and may not apply to everyone else’s crashing but I noticed that Docker started crashing when I added the following and stopped crashing when I removed it.
When it crashed, the output was:
Hey @kevinsimper. I unfortunately never made it anywhere in terms of actually fixing the issue. I’m running with Docker so I just set the thing to restart on error … which is ugly but has been working for my use case. Not sure if it is a version or resource issue.
I think this problem is related to memory. I had the same problem on VPS with 512 MB RAM but it never happened again on VPS with over 1024 MB RAM.
Did you figure this out? I have the same problem (but not with splash) on Circleci but not on Virtualbox 😦