Chromium fails to start subprocess --type=renderer at random, with no particular reason at all - Linux 64 - CentOS - no window manager

[Jean Marcel Duvoisin Schmidt]

3:35 PM (1 hour ago)

Hi folks,

I'm developing a embedded application using Chromium as a front-end. But for some reason it sometimes fails to start and seems to be stuck, without rendering anything. The booting process are as follows:

CentOS 7 - boots normally,

/etc/rc.d/rc.local -> calls /etc/rc.d/rc.MyScript

/etc/rc.d/rc.MyScript:

#!/bin/bash


XAUTHORITY=$HOME/.Xauthority
export XAUTHORITY


/etc/opt/elo-ser/setup/loadelo
/etc/opt/elo-ser/eloser ttyS1


openvpn --config /etc/openvpn/client.conf --daemon --auth-user-pass <(/usr/bin/python /usr/local/openvpn_login)


rm -rf /root/.serverauth* \
    /root/.Xauthority

su -l -s /bin/bash -c "/bin/xinit /root/.xinitrc -- /usr/bin/X :0 -auth $XAUTHORITY" root &>/root/.boot &



with being /root/.xinitrc:

#!/bin/bash

export HOME=/root

sleep 1 #ok, this is ugly, but for the tests now...

/usr/bin/display -geometry '1024x768+0+0!' -size '1024x768' /etc/splash.png &

sleep 5

/etc/opt/elo-ser/setup/eloxevent --xwarppointer

sleep 10

while true; do

# Clean up previously running apps, gracefully at first then harshly

killall -TERM chromium 2>/dev/null;

sleep 2;

killall -9 chromium 2>/dev/null;

killall -TERM /usr/bin/display

killall -9 /usr/bin/display

chromium-browser --no-sandbox "--app=$(cat /home/myapp/default_url)" --disk-cache-size=0 --media-cache-size=0 

done;

So in summary, Chromium is the only client of X server, running without any window manager, in application mode, running as root, same for the X server. Most of the times it simply works, and the application starts full-screen really well. Sometimes it does not, but killing chromium-browser processes makes them start again (the while on /root/.xinitrc) and then it works fine. I took two screenshots, when it does work and when it does not:

Paying attention, it is easy to note that one process of the four starts as --type=renderer and in the other case it simply starts as a common process. This pattern repeats itself over and over when it does work and when it does not. So seems that for a unknown reason, chromium is failing to start a renderer process.

Anyone have any tips where should I look for? Or what am I doing wrong?

Thanks for the reply!