Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 42 users
Status: Fixed
Owner: ----
Closed: Oct 2008
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment
The application failed to initialize properly (0xC0000005). Sandbox conflict with Symantec Security.
Reported by alele...@gmail.com, Sep 2 2008 Back to list
Product Version      : 0.2.149.27
URLs (if applicable) : N/A

What steps will reproduce the problem?
1. Windows XP SP3
2. Right after I installed Google Chrome Web Browser
3. Double click on Chrome icon

What is the expected result?

Error dialog raises:
   "The application failed to initialize properly (0x00000005).  Press on
Ok to terminate application."

What happens instead?
   Nothing else happens...


 
 
chrome2.jpg
35.7 KB View Download
chrome1.jpg
38.6 KB View Download
Same here in Vista SP1. Want to compare notes?
Comment 2 by chin...@gmail.com, Sep 2 2008
I'm getting the same error message for Windows XP SP2.
Comment 3 by vas...@gmail.com, Sep 2 2008
Same here with Windows Vista Ultimate SP1
Comment 4 Deleted
Comment 5 by Deleted ...@, Sep 2 2008
Same. Windows XP SP2.

Also, a friend/co-worker has same problem.
Comment 6 by vas...@gmail.com, Sep 2 2008
Same on my Windows XP box, both have Symantec Endpoint btw
Comment 7 by alele...@gmail.com, Sep 2 2008
Well I have Symantec Endpoint too...
Comment 8 by chin...@gmail.com, Sep 2 2008
Interesting.  I am running Symantec Endpoint as well!
Same issue (xp sp3).  Also running Symantec Endpoint.  
Error occurs every time you try to load any web page. XP SP3 with Symantec Endpoint.
Unauthorized NT call rejected by protection driver. 
Caller Process:
chrome.exe

Parameter:
FuncID=74H, RetAddr=17005CH 
as u see symantec is blocking the processes from executing with its protection driver
And so symantec it is...let's see....
Confirmed. 
Comment 15 by chin...@gmail.com, Sep 2 2008
I tried adding chrome.exe to the exceptions list, but that didn't seem to work.
Comment 16 by Deleted ...@, Sep 2 2008
I've disabled Endpoint Protection completely and it still doesn't start.
Comment 17 by Deleted ...@, Sep 2 2008
I am using a similar setup to the other users (XP3, Sym Endpoint Protection), but
disabling SEP didn't resolve the issue. Attempted multiple uninstalls, epic fail.
I see the same problem, with FuncID=BAH.
You must uninstall application protection within add/remove programs for chrome to 
work
Comment 20 by chin...@gmail.com, Sep 2 2008
Unfortunately, uninstalling application protection is not always an option in an
enterprise environment...
Same situation here. Win XP SP3, Win 2008 Srv.
Symantec Endpoint Protection v11

Unauthorized NT call rejected by protection driver. 
Caller Process: chrome.exe
Parameter: FuncID=74H, RetAddr=17005CH 

Same issue.
Windows XP, SP 2
Symantec Endpoint Protection also
Same issue as original poster.  XP SP3, SEP v11
Comment 24 by Deleted ...@, Sep 3 2008
Same issue, XP SP3 symantec endpoint protection
Comment 25 by cja...@gmail.com, Sep 3 2008
Adding a global exception in SEP didn't fix.


Labels: -Area-Unknown Area-AppCompat
Status: Assigned
You can try running Google Chrome with --no-sandbox (you need to edit the properties 
of the shortcut you use to launch it).

It looks like a conflict between some DLL injection or hooking that Symantec is doing 
(probably to monitor the app in the name of security) and the sandbox.  

If --no-sandbox does not fix things, another theory is that Symantec's monitor has 
some rule along the lines of "unknown software that tries to use the network should 
be terminated." I'd expect a notification to the user in that case, though.

In any event, this looks like a but we'll have to talk to Symantec about resolving. 
I'll take it and see what I can do.
Summary: The application failed to initialize properly (0xC0000005). (was: NULL)


Keyword: C0000005
(I am just trying to assist people in finding this issue - it seems like the search 
does not search by substring, so searching for C0000005 (without the 0x prefix) would 
not reveal this issue).
I am facing the same problem! and i have Symantec too
I'm using symantec too and had same error
but I resolved the problem with --no-sandbox as above.
Comment 31 by Deleted ...@, Sep 3 2008
I am running Vista SP1 and SEP11. Modifying the shortcut with --no-sandbox is
allowing me to start the browser now. I am not sure what the setting does, but would
be interested to learn more.
Comment 32 by Deleted ...@, Sep 3 2008
Hello,

The same error "The application failed to initialize properly (0x00000005).  Press on
Ok to terminate application."

what is --no-sandbox 
Comment 33 by Deleted ...@, Sep 3 2008
+1 Also running XP with SEP and the --no-sandbox fixed the issue for me.
Comment 34 by Deleted ...@, Sep 3 2008
Hello,

what is --no-sandbox 
Comment 35 by Deleted ...@, Sep 3 2008
Hello,

How to use --no-sandbox 
Comment 36 by Deleted ...@, Sep 3 2008
I asking for help .
Could you help me to solve the problem with chrome.exe
Comment 37 by Deleted ...@, Sep 3 2008
what is --no-sandbox 

Comment 38 by Deleted ...@, Sep 3 2008
Adding --no-sandbox at the end of the "target" line in the Google Chrome shortcut on 
the desktop icon.  This work around works for my PC w/ XP, SP3, SEP 11.0.2010.25.
Comment 39 by Deleted ...@, Sep 3 2008
Right click your shortcut to "Google Chrome" and click Properties.  In the target
text field, add a space then --no-sandbox right after the ending quotation mark.  Run
using this shortcut and it should work :)
Comment 40 by Deleted ...@, Sep 3 2008
it works....but not sure about the role of --no-sandbox. need more info....
Comment 41 by Deleted ...@, Sep 3 2008
Thank you it works
Comment 42 by Deleted ...@, Sep 3 2008
Thank you it works.
could you explain the role of --no-sandbox
No joy..
I am using Vista Business SP1 with Symantec SEP11
Running chrome --no-sandbox doesnt seem to fix this for me.
Labels: -OS-All OS-Windows
Summary: The application failed to initialize properly (0xC0000005). Sandbox conflict with Symantec Security. (was: NULL)
Comment 45 by Deleted ...@, Sep 3 2008
works like a charm..
Comment 46 by Deleted ...@, Sep 3 2008
I have window's vista business SP1, Symantec version 11.0.2000.1567
running chrome with --no-sandbox works fine. 
Make sure you submit a space after the .exe target
Comment 47 by Deleted ...@, Sep 3 2008
If you are having trouble making the sandbox workaround work - make sure you closed
out of Chrome, then relaunch. 
Comment 48 by Deleted ...@, Sep 3 2008
Thanks, --no-sandbox worked.
Comment 49 by Deleted ...@, Sep 3 2008
thanks, this helped!
Symantec says these steps will fix this issue:
https://forums.symantec.com/syment/board/message?board.id=endpoint_protection11&thread.id=15816

1) Back up the registry on an affected system.
2) Open the registry on the Agent system by entering regedit from a run prompt.
3) Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysPlant.
4) Open the Start DWORD.
5) Change the value to 4 to disable the drivers.
6) Reboot the system to commit the changes.
Comment 51 by Deleted ...@, Sep 3 2008
The fix from symantec I assume will only work for unmanaged clients. A managed 
client would reset the reg key on the next policy update.
The no sandbox parameter worked for me.  But it seems that disabling a security 
feature of the application to run it is completely unacceptable.  Am I now more 
susceptible to plugin malware or viruses?  It seems like compatibility with the 
nation's largest anti-virus software company would have been tested before release.  
But I do like the browser and the effort to increase competition out there.  I'm 
sure I will love what's to come with the browser.  But until this is fixed, I'm 
saying 'no' to using it for any secure transactions or browsing anything out of the 
ordinary.  Please don't be the new MS and blame Symantec.  There's got to be a way 
to resolve the issue kindly.  Thanks!!!!
The   --no-sandbox    fix works fine!  Thank you!
Comment 54 by Deleted ...@, Sep 3 2008
create a .reg file and put inside the following text and execute it.


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysPlant]
"Start"=dword:00000004


enjoy chrome !!
Hi there, I have created a simple Windows GUI (2 buttons) that let you choose how to
fix the problem. Please read more in this post
http://webreflection.blogspot.com/2008/09/google-chrome-fix.html

Kind Regards
Comment 56 Deleted
Comment 57 by Deleted ...@, Sep 3 2008
Thanks Andrea - your little app works like a charm.
Hi,

The --no-sandbox option disables the sandbox for the renderer process. That means 
that a flaw in the HTML rendering or Javascript engine could possibly affect your 
system since these 2 modules are not running inside the low-privilege sandbox.

We do not suggest to use this option, this is mostly used for testing.  That said, 
you can use it if you want. Just be careful about what pages you are browsing... and 
don't forget to stop using it when this bug gets fixed.

This option does not change anything for the plugins.

Running the no-sandbox option disables a special security feature of Chrome, so this 
might not be the best way to fix it.

http://blogoscoped.com/google-chrome/26
Comment 60 by part...@gmail.com, Sep 3 2008
Thanks Andrea!!!
Comment 61 by Deleted ...@, Sep 3 2008
regarding the comment from beanjosh...

"It seems like compatibility with the 
nation's largest anti-virus software company would have been tested before release."

This is a beta version - problems like these are exactly why it is released!  To find 
bugs and fix them.
exactly, it would be kind of hard for google to test Google Chrome on thousands of 
different computer configurations and thousands of types of software, this is the 
best time for testing 
I add to the last comment of Chorton95.  Chrome looks simple, fast, sleek, and light.
 I completely love the vision of Google and hope that this browser reaches its full.
Comment 64 Deleted
The registry modification in comment 50 (Via the program linked in comment 55) fixed 
this issue and  issue #124  for me.

Comment 66 by Deleted ...@, Sep 3 2008
the --no-sandbox worked for me, thnks a lot
Comment 67 by Deleted ...@, Sep 4 2008
 Issue #124  was marked as a duplicate of this issue.  However, I do not have
Symantec/Norton on this machine, I do not have a SysPlant key in the registry, and I
do not get the same error messages listed here.  While the --no-sandbox option does
seem to make things work, I'm not comfortable doing any further real-world testing
without the sandboxing environment operational.  I'll be anxious to see a fix for
this and to see what it was in the code.  Thanks.
The --no-sandbox worked for me. I also have Symantec End Point on my laptop with 
Windows XP SP2.

Comment 70 by Deleted ...@, Sep 4 2008
The --no-sandbox also worked for me. I also have Symantec EndPoint, HP DX5150, XP
Professional, SP3

Priority 2? Come on . . . it makes it impossible to install Google Chrome on 
thousands of machines. Surely this is worth an escalation!
Comment 72 by Deleted ...@, Sep 5 2008
its beta ~~ this is expected
Comment 73 by Deleted ...@, Sep 5 2008
Are Google products ever *not* beta?
Comment 74 by Deleted ...@, Sep 5 2008
Google isn't too blame for this... SEP is.
Comment 75 by Deleted ...@, Sep 5 2008
It's BETA, these kind of problems are going to happen. No-one is to "blame" for this,
it's BETA. Symantec protects your machine from rogue software hooking onto the stack
, chrome is a piece of malware in symantec's eyes, and rightfully so. Symantec will
be releasing an update to address this issue or google will stop violating whatever
rules it is breaking with the "Protection" software. It's beta...get over it. The fix
will come. However , you should not be bypassing security protocols to surf the web
on a beta browser on a machine unless you are willing to expose the machine
completely to the internet.
Comment 76 by Deleted ...@, Sep 7 2008
i have no Symantec software. and i dont even have any such registery key as hiven in
comment 50-53 
but i do have comodo firewall, and antivir. are they responsible?
Comment 77 by Deleted ...@, Sep 8 2008
The problem is SEP - see the article here on how to fix it form SEP's site:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008090310121448

Worked for me (running xp pro with SEP 11)
I have Windows XP, SP3 - Running Trend Micro Client/Server Security Agent which 
causes an "Ah Snap" message on any web page.  Chrome worked the first time I tried it 
and then the error every time.  The "--no-sandbox" allows Chrome to run.  
Comment 79 by Deleted ...@, Sep 9 2008
super thanks... no sandbox helped !!


D
Comment 80 by sethg...@gmail.com, Sep 12 2008
the "--no-sandbox" works brilliantly. THANKS!!!!!!! just don't go to sites you don't
know/trust. and here I thought my IT dept @ work had killed Chrome.
Comment 81 by Deleted ...@, Sep 14 2008
The issue of running Google Chrome with Windows XP SP3 is because of a process 
"ctfmon.exe"

To resolve the issue of Google Chrome running with Windows XP SP3 can be resolved by 
following steps:
- Goto Run
- Type "regsvr32 /U msimtf.dll"
- Click on OK
Again,
- Goto Run
- Type regsvr32 /U msctf.dll
- Click on OK

- Now, Reboot the Machine

This will resolve the problem and Google Chrome will start working normally.
Comment 82 Deleted
I also updated to Symantec Endpoint 11.0.3001_MR3 but this did not solve the problem
for me. Running Vista SP1.
Comment 84 Deleted
Labels: Area-BrowserBackend AppCompat
Changing to Area-BrowserBackend plus a dedicated AppCompat label because 
there are too many Area- labels.
Labels: -Area-AppCompat
Comment 87 by Deleted ...@, Oct 1 2008
The --no-sandbox also worked for me. I also have Symantec EndPoint, HP , XP
Professional, SP3
Comment 88 by Deleted ...@, Oct 12 2008
Same issue.. Have XP SP3 and Chrome does not work!
Comment 89 by hkd...@gmail.com, Oct 12 2008
I just installed SEP 11.0.3001.2224 in combination with Chrome 0.3.154.0.  I can 
finally say that I no longer need the no sandbox option.  If anyone else has a chance 
to verify, this is a first for me.  I will be installing on other machines today to 
see if this behavior is consistent.
Status: Fixed
The issue with Symantec Endpoint Protection should be resolved by their MR3 release: 

https://forums.symantec.com/syment/board/message?board.id=endpoint_protection11&thread.id=2733

If you see similar symptoms, but do not have Symantec's software installed, please file a separate issue.
Comment 92 Deleted
issue is NOT fixed for me with MR3 update on Windows Vista
Comment 94 by Deleted ...@, Oct 17 2008
I am not able to use Chrome..... I tried even by disabling Symante...but things do 
not work. I have Win XP with SP3
Comment 95 by Deleted ...@, Oct 20 2008
Hi,

I'm using MSWindows Vista 64 (SP1) with Symantec Endpoint 11.0.780.1109 and Chrome
runs perfectly. No workarounds, not a single change I did to get it running.
Comment 96 by rfi...@gmail.com, Oct 31 2008
i've update the SEP to MR3. It's fixed and NO NEED to use --no-sandbox anymore. I'm 
used XP3 and SEP 11.0.3001.2224

 Issue 4770  has been merged into this issue.
"--no-sandbox" its working for me also thanks for comment
Comment 99 by Deleted ...@, Feb 8 2009
I am having the same problem also. 
Windows XP SP3 Norton Internet Security 2009
Using the --no-sandbox workaround worked, but i really do not trust that. 
Comment 100 by cpu@chromium.org, Feb 13 2009
Jason,

Have you tried uninstalling or disabling NIS 2009 ?

You are the only report of this situation so far. 
The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=9733 

------------------------------------------------------------------------
r9733 | cpu@google.com | 2009-02-12 18:01:41 -0800 (Thu, 12 Feb 2009) | 8 lines
Changed paths:
   A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/installer/util/compat_checks.cc
   A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/installer/util/compat_checks.h
   A http://src.chromium.org/viewvc/chrome/trunk/src/chrome/installer/util/compat_checks_unittest.cc
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/installer/util/installer_unittests.vcproj?r1=9733&r2=9732
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/installer/util/util.vcproj?r1=9733&r2=9732

Test for Symantec SEP
- Versions before 11MR3 crash chrome
- Still need to wire the code.

BUG= 38 


Review URL: http://codereview.chromium.org/24015
------------------------------------------------------------------------

Comment 102 by mco...@gmail.com, Feb 13 2009
Guys, this is fixed after SEP MR4
Comment 103 by Deleted ...@, Feb 25 2009
how do i change and apply the --no-sandbox to my google chrome so it works.

Chukay
Comment 104 by dhw@chromium.org, Jul 16 2009
 Issue 13405  has been merged into this issue.
Comment 105 by Deleted ...@, Jul 18 2009
its not just symentec, it can also happen
if u r infrcted by

Internet worm W32.Netsky

chrome was working fine, until i got infected. the issue happened again after i 
formatted the system and i got infected again.
symentec and virus are related?/trying to start the same information sending 
process??
enlighten me!
Labels: -Area-BrowserBackend Area-Internals
Comment 107 by Deleted ...@, Jan 20 2010
it works with --no-sandbox
Comment 108 by Deleted ...@, Feb 20 2010
Don't have Symantec endpoint, and the "No sandbox" fix doesn't work for me. Running
Windows XP Sp3
Comment 109 by Deleted ...@, May 31 2010
same problem found under winxp sp3 + McaFee... IE is fine to run
Does anyone know if the --no-sandbox flag can be passed into Google ChromeFrame in IE?  We're having this issue with a client, and they are using ChromeFrame, not the Chrome browser.

Thanks.

Comment 111 Deleted
Actually nobody of you is listening. I'm an IRC Operator and I've got a user asking about that, so I tried to help him. When I googled the error I found this thread. He isn't using Symantec, so I suggested the no sandbox and it worked for him, but he wasn't convinced. I kept reading until I found vishwarup's comment (Sep 14, 2008):

./---------------------------------------------\.
The issue of running Google Chrome with Windows XP SP3 is because of a process 
"ctfmon.exe"

To resolve the issue of Google Chrome running with Windows XP SP3 can be resolved by 
following steps:
- Goto Run
- Type "regsvr32 /U msimtf.dll"
- Click on OK
Again,
- Goto Run
- Type regsvr32 /U msctf.dll
- Click on OK

- Now, Reboot the Machine

This will resolve the problem and Google Chrome will start working normally.
./---------------------------------------------\.

I asked the user then to do that since it seems safe and after rebooting he came back with a smiley face and a thanks.

Try it if you're facing this issue.

Thank you.
Project Member Comment 113 by bugdroid1@chromium.org, Oct 12 2012
Labels: Restrict-AddIssueComment-Commit
Owner: ----
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member Comment 114 by bugdroid1@chromium.org, Mar 10 2013
Labels: -Area-Internals Cr-Internals
Project Member Comment 115 by bugdroid1@chromium.org, Jul 16 2016
Labels: merge-merged-chromeos-3.14
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/3ffa6426c875c41dbc5fce40785cd46771a5ac14

commit 3ffa6426c875c41dbc5fce40785cd46771a5ac14
Author: Li Zefan <lizefan@huawei.com>
Date: Thu Sep 04 06:43:07 2014

UPSTREAM: cgroup: delay the clearing of cgrp->kn->priv

Run these two scripts concurrently:

    for ((; ;))
    {
        mkdir /cgroup/sub
        rmdir /cgroup/sub
    }

    for ((; ;))
    {
        echo $$ > /cgroup/sub/cgroup.procs
        echo $$ > /cgroup/cgroup.procs
    }

A kernel bug will be triggered:

BUG: unable to handle kernel NULL pointer dereference at 00000038
IP: [<c10bbd69>] cgroup_put+0x9/0x80
...
Call Trace:
 [<c10bbe19>] cgroup_kn_unlock+0x39/0x50
 [<c10bbe91>] cgroup_kn_lock_live+0x61/0x70
 [<c10be3c1>] __cgroup_procs_write.isra.26+0x51/0x230
 [<c10be5b2>] cgroup_tasks_write+0x12/0x20
 [<c10bb7b0>] cgroup_file_write+0x40/0x130
 [<c11aee71>] kernfs_fop_write+0xd1/0x160
 [<c1148e58>] vfs_write+0x98/0x1e0
 [<c114934d>] SyS_write+0x4d/0xa0
 [<c16f656b>] sysenter_do_call+0x12/0x12

We clear cgrp->kn->priv in the end of cgroup_rmdir(), but another
concurrent thread can access kn->priv after the clearing.

We should move the clearing to css_release_work_fn(). At that time
no one is holding reference to the cgroup and no one can gain a new
reference to access it.

v2:
- move RCU_INIT_POINTER() into the else block. (Tejun)
- remove the cgroup_parent() check. (Tejun)
- update the comment in css_tryget_online_from_dir().

Cc: <stable@vger.kernel.org> # 3.15+
Reported-by: Toralf Frster <toralf.foerster@gmx.de>
Signed-off-by: Zefan Li <lizefan@huawei.com>
Signed-off-by: Tejun Heo <tj@kernel.org>

BUG=b:29259708
TEST=Built and booted Minnie

(cherry picked from commit a4189487da1b4f8260c6006b9dc47c3c4107a5ae)
Signed-off-by: Dmitry Torokhov <dtor@chromium.org>
Change-Id: Iba57bd2781d18c234ab8739b8d609793a89eab53
Reviewed-on: https://chromium-review.googlesource.com/359880
Reviewed-by: Dylan Reid <dgreid@chromium.org>

[modify] https://crrev.com/3ffa6426c875c41dbc5fce40785cd46771a5ac14/kernel/cgroup.c

Project Member Comment 117 by bugdroid1@chromium.org, Mar 28
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e774f07c97a47852ad648879cba168424df0bf08

commit e774f07c97a47852ad648879cba168424df0bf08
Author: grt <grt@chromium.org>
Date: Tue Mar 28 19:45:13 2017

Remove Symantec SEP compat check code -- it was never wired up.

BUG= 38 

Review-Url: https://codereview.chromium.org/2784453003
Cr-Commit-Position: refs/heads/master@{#460191}

[delete] https://crrev.com/54b5563663f325d159f01efa846e74c803c65119/chrome/installer/setup/compat_checks_unittest.cc

Sign in to add a comment