Getting an error: You are using an unsupported command-line flag: --no-sandbox, Stability and security will suffer

[Ankit Goel]

Hi All,

I was getting an error "Ah SNAP" on every page of the chrome browser but to resolve that issue I followed some suggestions provided on the internet with which I have added "--no-sandbox" flag.

Could you please help to get this corrected so I should not face "Ah!! SNAP" error again?

Regards,

Ankit Goel

[PhistucK]

If it were simple or obvious, you would have found the answer already, so I guess this bug requires an investigation.

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[kosit la-orngsri]

เมื่อ วันอังคารที่ 17 ธันวาคม ค.ศ. 2019 15 นาฬิกา 24 นาที 17 วินาที UTC+7, Ankit Goel เขียนว่า:

[Alex Gough]

Hi Ankit,

We do not recommend running Chrome with the --no-sandbox flag.

You may be seeing incompatibility between RendererCodeIntegrity and third party software on your machine.

If you are running Symantec Endpoint Protection, please see https://support.symantec.com/us/en/article.tech256047.html

Otherwise please see https://crbug.com/1033717 to confirm if RendererCodeIntegrity is the root cause, where we'd appreciate some feedback.

Alex

On Tuesday, December 17, 2019 at 12:37:20 AM UTC-8, PhistucK wrote:

If it were simple or obvious, you would have found the answer already, so I guess this bug requires an investigation.

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

On Tue, Dec 17, 2019 at 10:24 AM Ankit Goel <ankit.goel.tech.1994@gmail.com> wrote:

Hi All,

I was getting an error "Ah SNAP" on every page of the chrome browser but to resolve that issue I followed some suggestions provided on the internet with which I have added "--no-sandbox" flag.

Could you please help to get this corrected so I should not face "Ah!! SNAP" error again?

Regards,

Ankit Goel

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.