Chrome sometimes doesn't start
Reported by
m.zd...@gmail.com,
Apr 21 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 Steps to reproduce the problem: 1. Setup pulseaudio sink pactl load-module module-null-sink sink_name=random123 pacmd update-sink-proplist random123 device.description=random123 2. Run Xvfb: Xvfb -nolisten tcp -screen 0 1024x576x24+32 & 3. Run window manager: ratpoison -d :0 & 4. Run browser from the commandline: DISPLAY=:0 PULSE_SINK=$MY_SINK google-chrome --kiosk --user-data-dir=/tmp/some-temp-nonexistent-directory --no-sandbox --no-zygote --allow-insecure-localhost --no-first-run --use-fake-ui-for-media-stream --disable-infobars --disable-gpu --v=1 --enable-logging=stderr https://www.example.com/ What is the expected behavior? Chrome should start and open the browser window. What went wrong? No browser window opens, google-chrome process hangs. Crashed report ID: no How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? No Chrome version: 58.0.3029.81 Channel: stable OS Version: Ubuntu 16.04.2 LTS; Kernel: 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Flash Version: Please see the attached files. One is from the failed startup (where chrome hangs without opening any window) and other from the successful startup. Estimated failed startup rate is 1 of 10. Same behaviour was with Google Chrome 57 (stable). Not sure about older versions. We are using this configuration to do browser session recording including audio using ffmpeg.
,
May 30 2017
Couldn't it be something with bluetooth detection? When the startup is successfull I see the following lines in the logs: ... (google-chrome:7504): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Could not connect: Connection refused [7504:7504:0530/145746.022684:VERBOSE1:bluez_dbus_manager.cc(172)] Bluetooth not supported. [7588:7588:0530/145746.024940:WARNING:chrome_main_delegate.cc(265)] process type 'renderer' should be created through the zygote. [7588:7588:0530/145746.025378:INFO:cpu_info.cc(50)] Available number of cores: 8 ... When it hangs on startup then the last lines are: ... [6771:6771:0530/145631.155767:WARNING:chrome_main_delegate.cc(265)] process type 'renderer' should be created through the zygote. [6771:6771:0530/145631.156242:INFO:cpu_info.cc(50)] Available number of cores: 8 Is there some commandline switch to prevent bluetooth detection so we could test it?
,
May 30 2017
It seems not to be a bluetooth problem. After installing bluez and starting it we don't get that message in the logs, but Chrome still sometimes hangs on startup.
Further investigation shows that main process waits on reading from pipe of which other end is at its child process.
Main process:
strace -p 30956
strace: Process 30956 attached
read(76,
Child process (found with (find /proc -type l | xargs ls -l | fgrep 'pipe:[3889257]') 2>/dev/null):
strace -p 31041
strace: Process 31041 attached
restart_syscall(<... resuming interrupted futex ...>) = -1 ETIMEDOUT (Connection timed out)
futex(0x5556acb44620, FUTEX_WAIT_PRIVATE, 2, {0, 5101582}) = -1 ETIMEDOUT (Connection timed out)
futex(0x5556acb44620, FUTEX_WAIT_PRIVATE, 2, {0, 5348721}) = -1 ETIMEDOUT (Connection timed out)
futex(0x5556acb44620, FUTEX_WAIT_PRIVATE, 2, {0, 12337845}) = -1 ETIMEDOUT (Connection timed out)
futex(0x5556acb44620, FUTEX_WAIT_PRIVATE, 2, {0, 2838682}) = -1 ETIMEDOUT (Connection timed out)
futex(0x5556acb44620, FUTEX_WAIT_PRIVATE, 2, {0, 14786082}) = -1 ETIMEDOUT (Connection timed out)
futex(0x5556acb44620, FUTEX_WAIT_PRIVATE, 2, {0, 6658581}) = -1 ETIMEDOUT (Connection timed out)
futex(0x5556acb44620, FUTEX_WAIT_PRIVATE, 2, {0, 4522016}) = -1 ETIMEDOUT (Connection timed out)
futex(0x5556acb44620, FUTEX_WAIT_PRIVATE, 2, {0, 5855620}) = -1 ETIMEDOUT (Connection timed out)
futex(0x5556acb44620, FUTEX_WAIT_PRIVATE, 2, {0, 10372735}) = -1 ETIMEDOUT (Connection timed out)
...
Please give us instructions what to do if you need any more details. Current Chrome version is Version 58.0.3029.110 (64-bit).
,
May 30 2017
Also it happens without using ratpoison or using special PULSE environment variables.
,
May 31 2017
We can't reproduce the issue with Chromium 58.0.3029.110.
,
Feb 15 2018
Clossing as per #5.
,
Feb 15 2018
Chromium 58 is OK but it is reproducible with Chrome 58. Where to report Chrome-only bugs? |
||
►
Sign in to add a comment |
||
Comment 1 by kavvaru@chromium.org
, Apr 21 2017