Issue metadata
Sign in to add a comment
|
zygote process should not be created with '--no-sandbox --no-zygote' flags
Reported by
wanchang...@lge.com,
Oct 16
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3582.0 Safari/537.36 Steps to reproduce the problem: 1. Launch chrome with flags '--no-sandbox --no-zygote' 2. Check zygote process existence by ps -ax command What is the expected behavior? Process with --type=zygote should not exist. What went wrong? When checking running process, process with --type=zygote exists Did this work before? Yes Chrome version: 72.0.3582.0 Channel: n/a OS Version: Flash Version:
,
Oct 16
I uploaded patch for this issue https://chromium-review.googlesource.com/c/chromium/src/+/1282687
,
Oct 16
,
Oct 16
,
Oct 17
wanchang.ryu@ Thanks for the issue... Tried to reproduce the issue on reported chrome version 72.0.3582.0 using Ubuntu 14.04. Attaching screen-cast for reference. Steps: --------- 1. Launched reported chrome with flags '--no-sandbox --no-zygote' 2. entered command in terminal > ps -ax As we are observed that chrome process not exist. @Reporter: Could you please check the attached screen cast and please let us know if anything missed from our end. Thanks..!
,
Oct 18
Hi phanindra.mandapaka, You need to launch another shell and exec 'ps -ax | grep chrome' to see the zygote process. $ ps -ax | grep chrome 24107 pts/19 S+ 0:01 xxxxx/chromium/src/out/Default/chrome --type=zygote --no-sandbox I expect that chrome shouldn't create the zygote process with flags of '--no-sandbox --no-zygote' Thanks.
,
Oct 18
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 18
wanchang.ryu@ Thanks for the feedback... As per comment #6, Tried to reproduce the issue on 72.0.3582.0 using Ubuntu 14.04. Attaching screenshot for reference. Steps: 1. Launched reported chrome with flags '--no-sandbox --no-zygote' 2. Opened another terminal and entered command > ps -ax | grep chrome @Reporter: As we are seen same behaviour from M-60 to reported chrome 72.0.3582.0 as per attached screenshot. Could you please have a look at the screenshots and let us know if the expected behaviour or Is the issue seen in both the versions. Your confirmation helps us to triage the issue further in a better way. Thanks...
,
Oct 18
I can say the issue exists in the screen shot. Could you check chrome 59 ? I think this version doesn't have the issue.
,
Oct 18
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 22
wanchang.ryu@ Thanks for the Confirmation... As per comment #9, Able to reproduce the issue on reported chrome version 72.0.3582.0 also on latest chrome 72.0.3586.0 using Ubuntu 14.04. Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged. Issue seen on Ubuntu and removing Needs-Bisect label to it. Thanks..!
,
Oct 25
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fc1b6354e001daa79df81cd5d8b025cc846da26b commit fc1b6354e001daa79df81cd5d8b025cc846da26b Author: Wanchang, Ryu <wanchang.ryu@lge.com> Date: Thu Oct 25 02:56:08 2018 Skip creating zygote with --no-zygote flag This CL fixed the side effect of https://chromium-review.googlesource.com/c/chromium/src/+/509529 By above commit, browser creates zygote process even with --no-sandbox --no-zygote flags. Zygote process should not be created with --no-sandbox --no-zygote flags. Bug: 895732 Change-Id: I2e2bebbab69b4ac5047cc33aa346942b83a67183 Reviewed-on: https://chromium-review.googlesource.com/c/1282687 Commit-Queue: Ken Rockot <rockot@google.com> Reviewed-by: Ken Rockot <rockot@google.com> Reviewed-by: Sami Kyöstilä <skyostil@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#602590} [modify] https://crrev.com/fc1b6354e001daa79df81cd5d8b025cc846da26b/content/app/content_main_runner_impl.cc [modify] https://crrev.com/fc1b6354e001daa79df81cd5d8b025cc846da26b/content/test/BUILD.gn [modify] https://crrev.com/fc1b6354e001daa79df81cd5d8b025cc846da26b/content/zygote/zygote_browsertest.cc [modify] https://crrev.com/fc1b6354e001daa79df81cd5d8b025cc846da26b/services/service_manager/zygote/host/zygote_host_impl_linux.h
,
Oct 25
I think this issue would be fixed by https://chromium-review.googlesource.com/c/1282687
,
Oct 25
Thanks for the fix! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by wanchang...@lge.com
, Oct 16