In Linux *without DBUS* chrome *sometimes* does not quits properly and leaves zombie processes (--type=zygote)
Reported by
lucas.va...@gmail.com,
Jan 6 2017
|
||||
Issue description
UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0
Steps to reproduce the problem:
1. unset DBUS_SESSION_BUS_ADDRESS
2. Xvfb :100
3. #!/bin/sh
while true; do
DISPLAY=:100 ./chrome &
X=$!
sleep 5s
kill $X
done
Wait for few minutes.
Happens to many users - see https://github.com/SeleniumHQ/docker-selenium/issues/87 and search for DBUS_SESSION_BUS_ADDRESS in comments.
What is the expected behavior?
chrome quits properly
What went wrong?
chrome --type=zygote zombie processes
Did this work before? N/A
Chrome version: 57.0.2950.4 Channel: dev
OS Version: ANY
Flash Version: Shockwave Flash 11.2 r202
don't even think about closing this as a duplicate of 86948 or similar, thanks!
,
Jan 6 2017
backtrace of the parent process of the zombie processes: (gdb) bt #0 0x00007f8738eff709 in ppoll () from /lib64/libc.so.6 #1 0x00007f874170034c in content::Zygote::ProcessRequests() () #2 0x00007f874170432e in content::ZygoteMain(content::MainFunctionParams const&, ScopedVector<content::ZygoteForkDelegate>) () #3 0x00007f8743fe9ba6 in content::RunZygote(content::MainFunctionParams const&, content::ContentMainDelegate*) () #4 0x00007f8743fead87 in content::ContentMainRunnerImpl::Run() () #5 0x00007f8743fe98c0 in content::ContentMain(content::ContentMainParams const&) () #6 0x00007f873ff8c38b in ChromeMain () #7 0x00007f8738e34b15 in __libc_start_main () from /lib64/libc.so.6 #8 0x00007f873ff8c269 in _start () NOTE: the problem goes away if you set DBUS_SESSION_BUS_ADDRESS (even to a nonsense value)
,
Jan 9 2017
,
Jan 11 2017
,
Feb 12 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 Deleted