For users with 0xc00000005 errors, as well as a few other errors, some
have found that turning off the sandbox resolves the issue.
However, please do not use the --no-sandbox option.
This option disables the low-privilege sandbox for showing web pages,
which leaves your
computer more vulnerable to flaws or security exploits on those pages.
It is intended for testing purposes only.
It's very important that Google Chrome is not run without the sandbox,
because of the inherent security vulnerabilities in that mode. We're
working very hard to fix the issues some of you are seeing, but in the
meantime, please don't use the --no-sandbox option.
> For users with 0xc00000005 errors, as well as a few other errors, some
> have found that turning off the sandbox resolves the issue.
> However, please do not use the --no-sandbox option.
> This option disables the low-privilege sandbox for showing web pages,
> which leaves your
> computer more vulnerable to flaws or security exploits on those pages.
> It is intended for testing purposes only.
> It's very important that Google Chrome is not run without the sandbox,
> because of the inherent security vulnerabilities in that mode. We're
> working very hard to fix the issues some of you are seeing, but in the
> meantime, please don't use the --no-sandbox option.
> For users with 0xc00000005 errors, as well as a few other errors, some
> have found that turning off the sandbox resolves the issue.
> However, please do not use the --no-sandbox option.
> This option disables the low-privilege sandbox for showing web pages,
> which leaves your
> computer more vulnerable to flaws or security exploits on those pages.
> It is intended for testing purposes only.
> It's very important that Google Chrome is not run without the sandbox,
> because of the inherent security vulnerabilities in that mode. We're
> working very hard to fix the issues some of you are seeing, but in the
> meantime, please don't use the --no-sandbox option.
Simon, many of us are experiencing the same thing as you. Namely, we
are NOT receiving the 0xc00000005 error but we are getting the "Aw
Snap" message for any document, whether it be html, txt, etc.
I really wish Google Group administrators would update the main
troubleshooting page and please add this issue as there are countless
users experiencing this problem. It is a distinct and separate issue
from those other people with the 0xc00000005 problem.
> I don't get 0xc00000005 or any other errors..but no web page loads
> with the "Aw Snap" message _unless_ I use "--no-sandbox".
> I've been using Chrome since it was released and didn't find any
> problem so far. Do you still think I should stop using Chrome?
> Regards,
> Sridhar.
> On Sep 10, 9:32 pm, Google Guide 2 wrote:
> > Hi all,
> > For users with 0xc00000005 errors, as well as a few other errors, some
> > have found that turning off the sandbox resolves the issue.
> > However, please do not use the --no-sandbox option.
> > This option disables the low-privilege sandbox for showing web pages,
> > which leaves your
> > computer more vulnerable to flaws or security exploits on those pages.
> > It is intended for testing purposes only.
> > It's very important that Google Chrome is not run without the sandbox,
> > because of the inherent security vulnerabilities in that mode. We're
> > working very hard to fix the issues some of you are seeing, but in the
> > meantime, please don't use the --no-sandbox option.
> For users with 0xc00000005 errors, as well as a few other errors, some
> have found that turning off thesandboxresolves the issue.
> However, please do not use the --no-sandboxoption.
> This option disables the low-privilegesandboxfor showing web pages,
> which leaves your
> computer more vulnerable to flaws or security exploits on those pages.
> It is intended for testing purposes only.
> It's very important that Google Chrome is not run without thesandbox,
> because of the inherent security vulnerabilities in that mode. We're
> working very hard to fix the issues some of you are seeing, but in the
> meantime, please don't use the --no-sandboxoption.
I took the opportunity to download the Chromium project and run the
debugger to see if I could find the problem. Personally, I'm not a
network engineer, however I found some things that might be useful in
helping to determine this problem. The debug output displays this
message as I try to load a page and get the Aw, Snap error:
[4080:1700:14183579:WARNING:ipc_channel.cc(156)] Connect called twice
I stepped into the code where this is called in Channel::Connect to
see if I could find the specific problem that was being reported.
Nothing was imediately obvious however in the call to
ProcessConnections() in the same method an error code of
ERROR_IO_PENDING was returned from a call to GetLastError().
I dug even further comming from the UI back and the code that draws
the Sad Tab. I found that sad tab was getting drawn due to a
render_view_host not being live. Digging into that I found that both
process_->channel() and render_initialized_ where returning NULL in
the call to IsRenderView() from WebContents::OnPaint().
I found this comment in the render_widget_host.h file that may explain
the reasons:
// The lifetime of the RenderWidgetHostHWND is tied to the render
process. If
// the render process dies, the RenderWidgetHostHWND goes away and all
// references to it must become NULL. If the WebContents finds itself
without a
// RenderWidgetHostHWND, it paints Sad Tab instead.
From the looks of the code, this doesn't really give you much
information, but not understanding the intricacies of how a web
browser obtains it's connection to a given server probably is
hindering me from gaining better answers at this point. I might get a
chance to play with this further, and I'll let you know if I do, as I
can easily reproduce this case both with the installed app, and with
the debug build of the app.
> For users with 0xc00000005 errors, as well as a few other errors, some
> have found that turning off the sandbox resolves the issue.
> However, please do not use the --no-sandbox option.
> This option disables the low-privilege sandbox for showing web pages,
> which leaves your
> computer more vulnerable to flaws or security exploits on those pages.
> It is intended for testing purposes only.
> It's very important that Google Chrome is not run without the sandbox,
> because of the inherent security vulnerabilities in that mode. We're
> working very hard to fix the issues some of you are seeing, but in the
> meantime, please don't use the --no-sandbox option.
Greetings Simon,
I posted some history in '0xc0000022 issue'; after 8 tries was finally
able to get Chrome to run using --no-sandbox; now I read don't use the
--no-sandbox argument. So what am I to use???
> For users with 0xc00000005 errors, as well as a few other errors, some
> have found that turning off the sandbox resolves the issue.
> However, please do not use the --no-sandbox option.
> This option disables the low-privilege sandbox for showing web pages,
> which leaves your
> computer more vulnerable to flaws or security exploits on those pages.
> It is intended for testing purposes only.
> It's very important that Google Chrome is not run without the sandbox,
> because of the inherent security vulnerabilities in that mode. We're
> working very hard to fix the issues some of you are seeing, but in the
> meantime, please don't use the --no-sandbox option.
"Aw Snap" error on every page points to a renderer crash -- why
exactly the renderer crashes is the mystery.
Let's try to collect as much system information as possible to see if
there are commonalities among those whose renderer crashes.
Toby-wan, thanks so much for the detail. I'll pass it around and see
what we can do with it.
Crltn, I understand how frustrating it can be to be told not to use a
workaround that seems to work so effectively. Since turning off
sandbox opens you to security risks, it's safer to not risk it.
Thanks everyone for your patience with these crashes -- hopefully
we'll find more leads on specific issues that cause renderer crashes.
> Greetings Simon,
> I posted some history in '0xc0000022 issue'; after 8 tries was finally
> able to get Chrome to run using --no-sandbox; now I read don't use the
> --no-sandbox argument. So what am I to use???
> Crltn
> On Sep 10, 8:32 am, Google Guide 2 wrote:
> > Hi all,
> > For users with 0xc00000005 errors, as well as a few other errors, some
> > have found that turning off the sandbox resolves the issue.
> > However, please do not use the --no-sandbox option.
> > This option disables the low-privilege sandbox for showing web pages,
> > which leaves your
> > computer more vulnerable to flaws or security exploits on those pages.
> > It is intended for testing purposes only.
> > It's very important that Google Chrome is not run without the sandbox,
> > because of the inherent security vulnerabilities in that mode. We're
> > working very hard to fix the issues some of you are seeing, but in the
> > meantime, please don't use the --no-sandbox option.
> "Aw Snap" error on every page points to a renderer crash -- why
> exactly the renderer crashes is the mystery.
> Let's try to collect as much system information as possible to see if
> there are commonalities among those whose renderer crashes.
> Toby-wan, thanks so much for the detail. I'll pass it around and see
> what we can do with it.
> Crltn, I understand how frustrating it can be to be told not to use a
> workaround that seems to work so effectively. Since turning off
> sandbox opens you to security risks, it's safer to not risk it.
> Thanks everyone for your patience with these crashes -- hopefully
> we'll find more leads on specific issues that cause renderer crashes.
> Simon
> On Sep 23, 9:24 pm, Crltn wrote:
> > Greetings Simon,
> > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > able to get Chrome to run using --no-sandbox; now I read don't use the
> > --no-sandbox argument. So what am I to use???
> > Crltn
> > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > Hi all,
> > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > have found that turning off the sandbox resolves the issue.
> > > However, please do not use the --no-sandbox option.
> > > This option disables the low-privilege sandbox for showing web pages,
> > > which leaves your
> > > computer more vulnerable to flaws or security exploits on those pages.
> > > It is intended for testing purposes only.
> > > It's very important that Google Chrome is not run without the sandbox,
> > > because of the inherent security vulnerabilities in that mode. We're
> > > working very hard to fix the issues some of you are seeing, but in the
> > > meantime, please don't use the --no-sandbox option.
It's a tough situation -- if you use Google Chrome without the
sandbox, you're opening yourself up to some heavy security risks. If
you don't turn off the sandbox, you have no choice but to use another
browser for the time being. I know it sounds strange for someone on
the Google Chrome team to recommend you use another browser in this
case, but I don't want your system to be compromised.
Have I shared this link yet? It's the pages in the Google Chrome comic
book that describe the sandbox.
Naturally, this is a top area of focus for me -- we've got to find out
what's causing these renderer crashes. It seems that software conflict
is a major suspect, so please share with us what other processes are
running on your system and we'll see if there are any commonalities.
> But then how are we supposed to use Google Chrome without the --no-
> sandbox option since we can't even load a single page without it?
> Thanks.
> On Oct 1, 1:55 am, Google Guide 2 wrote:
> > Hi Sridhar,
> > "Aw Snap" error on every page points to a renderer crash -- why
> > exactly the renderer crashes is the mystery.
> > Let's try to collect as much system information as possible to see if
> > there are commonalities among those whose renderer crashes.
> > Toby-wan, thanks so much for the detail. I'll pass it around and see
> > what we can do with it.
> > Crltn, I understand how frustrating it can be to be told not to use a
> > workaround that seems to work so effectively. Since turning off
> > sandbox opens you to security risks, it's safer to not risk it.
> > Thanks everyone for your patience with these crashes -- hopefully
> > we'll find more leads on specific issues that cause renderer crashes.
> > Simon
> > On Sep 23, 9:24 pm, Crltn wrote:
> > > Greetings Simon,
> > > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > > able to get Chrome to run using --no-sandbox; now I read don't use the
> > > --no-sandbox argument. So what am I to use???
> > > Crltn
> > > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > > Hi all,
> > > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > > have found that turning off the sandbox resolves the issue.
> > > > However, please do not use the --no-sandbox option.
> > > > This option disables the low-privilege sandbox for showing web pages,
> > > > which leaves your
> > > > computer more vulnerable to flaws or security exploits on those pages.
> > > > It is intended for testing purposes only.
> > > > It's very important that Google Chrome is not run without the sandbox,
> > > > because of the inherent security vulnerabilities in that mode. We're
> > > > working very hard to fix the issues some of you are seeing, but in the
> > > > meantime, please don't use the --no-sandbox option.
Someone in another topic discovered that this problem can be avoided
by starting the renderers manually, so the problem may be in the code
that launches the renderer process. (Maybe a short buffer for the
arguments?)
I verified that this workaround also works in Wine.
> It's a tough situation -- if you use Google Chrome without the
> sandbox, you're opening yourself up to some heavy security risks. If
> you don't turn off the sandbox, you have no choice but to use another
> browser for the time being. I know it sounds strange for someone on
> the Google Chrome team to recommend you use another browser in this
> case, but I don't want your system to be compromised.
> Have I shared this link yet? It's the pages in the Google Chrome comic
> book that describe the sandbox.
> Naturally, this is a top area of focus for me -- we've got to find out
> what's causing these renderer crashes. It seems that software conflict
> is a major suspect, so please share with us what other processes are
> running on your system and we'll see if there are any commonalities.
> Thanks for understanding,
> Simon
> On Sep 30, 9:27 pm, StealthWind wrote:
> > But then how are we supposed to use Google Chrome without the --no-
> > sandbox option since we can't even load a single page without it?
> > Thanks.
> > On Oct 1, 1:55 am, Google Guide 2 wrote:
> > > Hi Sridhar,
> > > "Aw Snap" error on every page points to a renderer crash -- why
> > > exactly the renderer crashes is the mystery.
> > > Let's try to collect as much system information as possible to see if
> > > there are commonalities among those whose renderer crashes.
> > > Toby-wan, thanks so much for the detail. I'll pass it around and see
> > > what we can do with it.
> > > Crltn, I understand how frustrating it can be to be told not to use a
> > > workaround that seems to work so effectively. Since turning off
> > > sandbox opens you to security risks, it's safer to not risk it.
> > > Thanks everyone for your patience with these crashes -- hopefully
> > > we'll find more leads on specific issues that cause renderer crashes.
> > > Simon
> > > On Sep 23, 9:24 pm, Crltn wrote:
> > > > Greetings Simon,
> > > > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > > > able to get Chrome to run using --no-sandbox; now I read don't use the
> > > > --no-sandbox argument. So what am I to use???
> > > > Crltn
> > > > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > > > Hi all,
> > > > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > > > have found that turning off the sandbox resolves the issue.
> > > > > However, please do not use the --no-sandbox option.
> > > > > This option disables the low-privilege sandbox for showing web pages,
> > > > > which leaves your
> > > > > computer more vulnerable to flaws or security exploits on those pages.
> > > > > It is intended for testing purposes only.
> > > > > It's very important that Google Chrome is not run without the sandbox,
> > > > > because of the inherent security vulnerabilities in that mode. We're
> > > > > working very hard to fix the issues some of you are seeing, but in the
> > > > > meantime, please don't use the --no-sandbox option.
I forgot in my earlier post to mention that I'm seeing this same
problem on all of the computers here in my office that are hooked up
to the domain. Not sure, but might have something to do with it.
Anyone else with the problem either always or sometimes connected to a
domain?
> It's a tough situation -- if you use Google Chrome without the
> sandbox, you're opening yourself up to some heavy security risks. If
> you don't turn off the sandbox, you have no choice but to use another
> browser for the time being. I know it sounds strange for someone on
> the Google Chrome team to recommend you use another browser in this
> case, but I don't want your system to be compromised.
> Have I shared this link yet? It's the pages in the Google Chrome comic
> book that describe the sandbox.
> Naturally, this is a top area of focus for me -- we've got to find out
> what's causing these renderer crashes. It seems that software conflict
> is a major suspect, so please share with us what other processes are
> running on your system and we'll see if there are any commonalities.
> Thanks for understanding,
> Simon
> On Sep 30, 9:27 pm, StealthWind wrote:
> > But then how are we supposed to use Google Chrome without the --no-
> > sandbox option since we can't even load a single page without it?
> > Thanks.
> > On Oct 1, 1:55 am, Google Guide 2 wrote:
> > > Hi Sridhar,
> > > "Aw Snap" error on every page points to a renderer crash -- why
> > > exactly the renderer crashes is the mystery.
> > > Let's try to collect as much system information as possible to see if
> > > there are commonalities among those whose renderer crashes.
> > > Toby-wan, thanks so much for the detail. I'll pass it around and see
> > > what we can do with it.
> > > Crltn, I understand how frustrating it can be to be told not to use a
> > > workaround that seems to work so effectively. Since turning off
> > > sandbox opens you to security risks, it's safer to not risk it.
> > > Thanks everyone for your patience with these crashes -- hopefully
> > > we'll find more leads on specific issues that cause renderer crashes.
> > > Simon
> > > On Sep 23, 9:24 pm, Crltn wrote:
> > > > Greetings Simon,
> > > > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > > > able to get Chrome to run using --no-sandbox; now I read don't use the
> > > > --no-sandbox argument. So what am I to use???
> > > > Crltn
> > > > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > > > Hi all,
> > > > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > > > have found that turning off the sandbox resolves the issue.
> > > > > However, please do not use the --no-sandbox option.
> > > > > This option disables the low-privilege sandbox for showing web pages,
> > > > > which leaves your
> > > > > computer more vulnerable to flaws or security exploits on those pages.
> > > > > It is intended for testing purposes only.
> > > > > It's very important that Google Chrome is not run without the sandbox,
> > > > > because of the inherent security vulnerabilities in that mode. We're
> > > > > working very hard to fix the issues some of you are seeing, but in the
> > > > > meantime, please don't use the --no-sandbox option.
> I forgot in my earlier post to mention that I'm seeing this same
> problem on all of the computers here in my office that are hooked up
> to the domain. Not sure, but might have something to do with it.
> Anyone else with the problem either always or sometimes connected to a
> domain?
> On Oct 1, 7:25 pm, Google Guide wrote:
> > Hi StealthWind,
> > It's a tough situation -- if you use Google Chrome without the
> > sandbox, you're opening yourself up to some heavy security risks. If
> > you don't turn off the sandbox, you have no choice but to use another
> > browser for the time being. I know it sounds strange for someone on
> > the Google Chrome team to recommend you use another browser in this
> > case, but I don't want your system to be compromised.
> > Have I shared this link yet? It's the pages in the Google Chrome comic
> > book that describe the sandbox.
> > Naturally, this is a top area of focus for me -- we've got to find out
> > what's causing these renderer crashes. It seems that software conflict
> > is a major suspect, so please share with us what other processes are
> > running on your system and we'll see if there are any commonalities.
> > Thanks for understanding,
> > Simon
> > On Sep 30, 9:27 pm, StealthWind wrote:
> > > But then how are we supposed to use Google Chrome without the --no-
> > > sandbox option since we can't even load a single page without it?
> > > Thanks.
> > > On Oct 1, 1:55 am, Google Guide 2 wrote:
> > > > Hi Sridhar,
> > > > "Aw Snap" error on every page points to a renderer crash -- why
> > > > exactly the renderer crashes is the mystery.
> > > > Let's try to collect as much system information as possible to see if
> > > > there are commonalities among those whose renderer crashes.
> > > > Toby-wan, thanks so much for the detail. I'll pass it around and see
> > > > what we can do with it.
> > > > Crltn, I understand how frustrating it can be to be told not to use a
> > > > workaround that seems to work so effectively. Since turning off
> > > > sandbox opens you to security risks, it's safer to not risk it.
> > > > Thanks everyone for your patience with these crashes -- hopefully
> > > > we'll find more leads on specific issues that cause renderer crashes.
> > > > Simon
> > > > On Sep 23, 9:24 pm, Crltn wrote:
> > > > > Greetings Simon,
> > > > > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > > > > able to get Chrome to run using --no-sandbox; now I read don't use the
> > > > > --no-sandbox argument. So what am I to use???
> > > > > Crltn
> > > > > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > > > > Hi all,
> > > > > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > > > > have found that turning off the sandbox resolves the issue.
> > > > > > However, please do not use the --no-sandbox option.
> > > > > > This option disables the low-privilege sandbox for showing web pages,
> > > > > > which leaves your
> > > > > > computer more vulnerable to flaws or security exploits on those pages.
> > > > > > It is intended for testing purposes only.
> > > > > > It's very important that Google Chrome is not run without the sandbox,
> > > > > > because of the inherent security vulnerabilities in that mode. We're
> > > > > > working very hard to fix the issues some of you are seeing, but in the
> > > > > > meantime, please don't use the --no-sandbox option.
For those of you experiencing the "Aww Snap" >> Renderer crash in
Google Chrome, it'd be helpful if you could peek in your Event Viewer,
and pass along a few crash ID's, (provided that one was generated.)
Here's how to locate the ID:
1. Click Start and select "Run."
2. Type "eventvwr" (without quotes) and press Enter. Event Viewer will
open.
3. Double click the "Application" tree to expand it.
4. Click the "Source" column on the right and scroll down the list
looking for events named "Chrome."
5. Double click the entry to see its details. (Look at the timestamp
to find recent crash events. If we're lucky, it will contain a crash
ID).
6. Paste the crash ID into this thread with your O/S and version of
Chrome.
Thanks very much for helping us get to the bottom of this issue!
Ben
> It's happening on all our office/domain machines also.
> I suspect it was blocked centrally somehow.
> On Oct 2, 7:50 pm, Toby-Wan wrote:
> > I forgot in my earlier post to mention that I'm seeing this same
> > problem on all of the computers here in my office that are hooked up
> > to the domain. Not sure, but might have something to do with it.
> > Anyone else with the problem either always or sometimes connected to a
> > domain?
> > On Oct 1, 7:25 pm, Google Guide wrote:
> > > Hi StealthWind,
> > > It's a tough situation -- if you use Google Chrome without the
> > > sandbox, you're opening yourself up to some heavy security risks. If
> > > you don't turn off the sandbox, you have no choice but to use another
> > > browser for the time being. I know it sounds strange for someone on
> > > the Google Chrome team to recommend you use another browser in this
> > > case, but I don't want your system to be compromised.
> > > Have I shared this link yet? It's the pages in the Google Chrome comic
> > > book that describe the sandbox.
> > > Naturally, this is a top area of focus for me -- we've got to find out
> > > what's causing these renderer crashes. It seems that software conflict
> > > is a major suspect, so please share with us what other processes are
> > > running on your system and we'll see if there are any commonalities.
> > > Thanks for understanding,
> > > Simon
> > > On Sep 30, 9:27 pm, StealthWind wrote:
> > > > But then how are we supposed to use Google Chrome without the --no-
> > > > sandbox option since we can't even load a single page without it?
> > > > Thanks.
> > > > On Oct 1, 1:55 am, Google Guide 2 wrote:
> > > > > Hi Sridhar,
> > > > > "Aw Snap" error on every page points to a renderer crash -- why
> > > > > exactly the renderer crashes is the mystery.
> > > > > Let's try to collect as much system information as possible to see if
> > > > > there are commonalities among those whose renderer crashes.
> > > > > Toby-wan, thanks so much for the detail. I'll pass it around and see
> > > > > what we can do with it.
> > > > > Crltn, I understand how frustrating it can be to be told not to use a
> > > > > workaround that seems to work so effectively. Since turning off
> > > > > sandbox opens you to security risks, it's safer to not risk it.
> > > > > Thanks everyone for your patience with these crashes -- hopefully
> > > > > we'll find more leads on specific issues that cause renderer crashes.
> > > > > Simon
> > > > > On Sep 23, 9:24 pm, Crltn wrote:
> > > > > > Greetings Simon,
> > > > > > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > > > > > able to get Chrome to run using --no-sandbox; now I read don't use the
> > > > > > --no-sandbox argument. So what am I to use???
> > > > > > Crltn
> > > > > > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > > > > > Hi all,
> > > > > > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > > > > > have found that turning off the sandbox resolves the issue.
> > > > > > > However, please do not use the --no-sandbox option.
> > > > > > > This option disables the low-privilege sandbox for showing web pages,
> > > > > > > which leaves your
> > > > > > > computer more vulnerable to flaws or security exploits on those pages.
> > > > > > > It is intended for testing purposes only.
> > > > > > > It's very important that Google Chrome is not run without the sandbox,
> > > > > > > because of the inherent security vulnerabilities in that mode. We're
> > > > > > > working very hard to fix the issues some of you are seeing, but in the
> > > > > > > meantime, please don't use the --no-sandbox option.
> For those of you experiencing the "Aww Snap" >> Renderer crash in
> Google Chrome, it'd be helpful if you could peek in your Event Viewer,
> and pass along a few crash ID's, (provided that one was generated.)
> Here's how to locate the ID:
> 1. Click Start and select "Run."
> 2. Type "eventvwr" (without quotes) and press Enter. Event Viewer will
> open.
> 3. Double click the "Application" tree to expand it.
> 4. Click the "Source" column on the right and scroll down the list
> looking for events named "Chrome."
> 5. Double click the entry to see its details. (Look at the timestamp
> to find recent crash events. If we're lucky, it will contain a crash
> ID).
> 6. Paste the crash ID into this thread with your O/S and version of
> Chrome.
> Thanks very much for helping us get to the bottom of this issue!
> Ben
> On Oct 3, 12:34 am, element1 wrote:
> > It's happening on all our office/domain machines also.
> > I suspect it was blocked centrally somehow.
> > On Oct 2, 7:50 pm, Toby-Wan wrote:
> > > I forgot in my earlier post to mention that I'm seeing this same
> > > problem on all of the computers here in my office that are hooked up
> > > to the domain. Not sure, but might have something to do with it.
> > > Anyone else with the problem either always or sometimes connected to a
> > > domain?
> > > On Oct 1, 7:25 pm, Google Guide wrote:
> > > > Hi StealthWind,
> > > > It's a tough situation -- if you use Google Chrome without the
> > > > sandbox, you're opening yourself up to some heavy security risks. If
> > > > you don't turn off the sandbox, you have no choice but to use another
> > > > browser for the time being. I know it sounds strange for someone on
> > > > the Google Chrome team to recommend you use another browser in this
> > > > case, but I don't want your system to be compromised.
> > > > Have I shared this link yet? It's the pages in the Google Chrome comic
> > > > book that describe the sandbox.
> > > > Naturally, this is a top area of focus for me -- we've got to find out
> > > > what's causing these renderer crashes. It seems that software conflict
> > > > is a major suspect, so please share with us what other processes are
> > > > running on your system and we'll see if there are any commonalities.
> > > > Thanks for understanding,
> > > > Simon
> > > > On Sep 30, 9:27 pm, StealthWind wrote:
> > > > > But then how are we supposed to use Google Chrome without the --no-
> > > > > sandbox option since we can't even load a single page without it?
> > > > > Thanks.
> > > > > On Oct 1, 1:55 am, Google Guide 2 wrote:
> > > > > > Hi Sridhar,
> > > > > > "Aw Snap" error on every page points to a renderer crash -- why
> > > > > > exactly the renderer crashes is the mystery.
> > > > > > Let's try to collect as much system information as possible to see if
> > > > > > there are commonalities among those whose renderer crashes.
> > > > > > Toby-wan, thanks so much for the detail. I'll pass it around and see
> > > > > > what we can do with it.
> > > > > > Crltn, I understand how frustrating it can be to be told not to use a
> > > > > > workaround that seems to work so effectively. Since turning off
> > > > > > sandbox opens you to security risks, it's safer to not risk it.
> > > > > > Thanks everyone for your patience with these crashes -- hopefully
> > > > > > we'll find more leads on specific issues that cause renderer crashes.
> > > > > > Simon
> > > > > > On Sep 23, 9:24 pm, Crltn wrote:
> > > > > > > Greetings Simon,
> > > > > > > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > > > > > > able to get Chrome to run using --no-sandbox; now I read don't use the
> > > > > > > --no-sandbox argument. So what am I to use???
> > > > > > > Crltn
> > > > > > > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > > > > > > Hi all,
> > > > > > > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > > > > > > have found that turning off the sandbox resolves the issue.
> > > > > > > > However, please do not use the --no-sandbox option.
> > > > > > > > This option disables the low-privilege sandbox for showing web pages,
> > > > > > > > which leaves your
> > > > > > > > computer more vulnerable to flaws or security exploits on those pages.
> > > > > > > > It is intended for testing purposes only.
> > > > > > > > It's very important that Google Chrome is not run without the sandbox,
> > > > > > > > because of the inherent security vulnerabilities in that mode. We're
> > > > > > > > working very hard to fix the issues some of you are seeing, but in the
> > > > > > > > meantime, please don't use the --no-sandbox option.
I cannot get Chrome to fail in a real Windows machine, but from what I
am seeing in Wine, the problem may be in
advapi:CreateRestrictedToken. That function is just a stub in Wine,
but is not called when Chrome is running with --no-sandbox.
Without either of those command lines I can get nothing. With either
of them everything appears to work fine.
Using the --in-process-plugins option I *can* create application
shortcuts from Chrome.. however, when launching one of the created
shortcuts.. I get nothing. Either it just remains with a "waiting for
www.xxxxxxx" or (in the case of making google.com an application
shortcut) appears to show up fine, but then becomes unusable and
eventually results in a 'Aw Snap'
Any time the application shortcut is launched, Chrome itself reverts
to the unusuable 'Aw Snap' state on every page. Regardless of whether
it remains open and the shortcut is launched or if everything was
closed down and Chrome was opened after trying to open the app.
shortcut.
I have also checked eventvwr and there is nothing in there for Chrome
anywhere. Sorry :(
Work machine: Yes
Norton: No
McAfee: No
OS: WinXP SP2
Proxy: (No - but I am behind the great firewall of China)
Full admin rights: Yes
I do hope the problem for this can be identified because it does
appear to be a lovely browser. But for now (and even writing this - I
am forced to remain with Firefox)
> bkennelly, in support of your theory, I just tried creating an
> application shortcut using the --no-sandbox option, and it didn't work
> either.
> Is there anyone that needs to run Chrome with the --no-sandbox or --in-
> process-plugins option who is able to create application shortcuts
> with the Chrome interface?
No trace in event viewer. If I start windows in safe mode with
networking I am able to see local html files.
Installation leaves "ERROR:setup.cc(282)] Return status of Chrome
browser registration 0" line in chrome_installer.log in temp
directory.
->When I click on "change google gears settings" in option I am
getting same "Aw,Snap" page.
> For those of you experiencing the "Aww Snap" >> Renderer crash in
> Google Chrome, it'd be helpful if you could peek in your Event Viewer,
> and pass along a few crash ID's, (provided that one was generated.)
> Here's how to locate the ID:
> 1. Click Start and select "Run."
> 2. Type "eventvwr" (without quotes) and press Enter. Event Viewer will
> open.
> 3. Double click the "Application" tree to expand it.
> 4. Click the "Source" column on the right and scroll down the list
> looking for events named "Chrome."
> 5. Double click the entry to see its details. (Look at the timestamp
> to find recent crash events. If we're lucky, it will contain a crash
> ID).
> 6. Paste the crash ID into this thread with your O/S and version of
> Chrome.
> Thanks very much for helping us get to the bottom of this issue!
> Ben
> On Oct 3, 12:34 am, element1 wrote:
> > It's happening on all our office/domain machines also.
> > I suspect it was blocked centrally somehow.
> > On Oct 2, 7:50 pm, Toby-Wan wrote:
> > > I forgot in my earlier post to mention that I'm seeing this same
> > > problem on all of the computers here in my office that are hooked up
> > > to the domain. Not sure, but might have something to do with it.
> > > Anyone else with the problem either always or sometimes connected to a
> > > domain?
> > > On Oct 1, 7:25 pm, Google Guide wrote:
> > > > Hi StealthWind,
> > > > It's a tough situation -- if you use Google Chrome without the
> > > > sandbox, you're opening yourself up to some heavy security risks. If
> > > > you don't turn off the sandbox, you have no choice but to use another
> > > > browser for the time being. I know it sounds strange for someone on
> > > > the Google Chrome team to recommend you use another browser in this
> > > > case, but I don't want your system to be compromised.
> > > > Have I shared this link yet? It's the pages in the Google Chrome comic
> > > > book that describe the sandbox.
> > > > Naturally, this is a top area of focus for me -- we've got to find out
> > > > what's causing these renderer crashes. It seems that software conflict
> > > > is a major suspect, so please share with us what other processes are
> > > > running on your system and we'll see if there are any commonalities.
> > > > Thanks for understanding,
> > > > Simon
> > > > On Sep 30, 9:27 pm, StealthWind wrote:
> > > > > But then how are we supposed to use Google Chrome without the --no-
> > > > > sandbox option since we can't even load a single page without it?
> > > > > Thanks.
> > > > > On Oct 1, 1:55 am, Google Guide 2 wrote:
> > > > > > Hi Sridhar,
> > > > > > "Aw Snap" error on every page points to a renderer crash -- why
> > > > > > exactly the renderer crashes is the mystery.
> > > > > > Let's try to collect as much system information as possible to see if
> > > > > > there are commonalities among those whose renderer crashes.
> > > > > > Toby-wan, thanks so much for the detail. I'll pass it around and see
> > > > > > what we can do with it.
> > > > > > Crltn, I understand how frustrating it can be to be told not to use a
> > > > > > workaround that seems to work so effectively. Since turning off
> > > > > > sandbox opens you to security risks, it's safer to not risk it.
> > > > > > Thanks everyone for your patience with these crashes -- hopefully
> > > > > > we'll find more leads on specific issues that cause renderer crashes.
> > > > > > Simon
> > > > > > On Sep 23, 9:24 pm, Crltn wrote:
> > > > > > > Greetings Simon,
> > > > > > > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > > > > > > able to get Chrome to run using --no-sandbox; now I read don't use the
> > > > > > > --no-sandbox argument. So what am I to use???
> > > > > > > Crltn
> > > > > > > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > > > > > > Hi all,
> > > > > > > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > > > > > > have found that turning off the sandbox resolves the issue.
> > > > > > > > However, please do not use the --no-sandbox option.
> > > > > > > > This option disables the low-privilege sandbox for showing web pages,
> > > > > > > > which leaves your
> > > > > > > > computer more vulnerable to flaws or security exploits on those pages.
> > > > > > > > It is intended for testing purposes only.
> > > > > > > > It's very important that Google Chrome is not run without the sandbox,
> > > > > > > > because of the inherent security vulnerabilities in that mode. We're
> > > > > > > > working very hard to fix the issues some of you are seeing, but in the
> > > > > > > > meantime, please don't use the --no-sandbox option.
I'm he guy from the other forum (http://groups.google.com/group/google- chrome-help-troubleshooting/browse_thread/thread/96a12b80dab6df6a/
ec17c809b6162b04?hl=en&q=aw%2C+snap&lnk=nl&#) who discovered he could
load web pages if he started the renderers manually. Since the other
group was directed here, I thought I'd post here and see if any of you
have similar luck with the "start-renderers-manually" switch. Thanks
bkennelly for verifying the workaround in wine!
My situation seams to be slightly different than some of you, because
I am unable to create application shortcuts - when I click on the menu
option, nothing happens. Like everyone who has posted before me, my
event viewer does not contain any chrome events.
I am running XP Pro on a Windows Server 2003 Domain.
Chrome is at version 0.2.149.30
Strangely enough, just recently I've been getting "Update Server not
Available (error 1)" at the office, where the browser doesn't work. At
home, where I have Chrome installed on two computers, I am not
experiencing any unexpected issues. Maybe it's just a fluke - I intend
to look into it when I get a chance.
> For those of you experiencing the "Aww Snap" >> Renderer crash in
> Google Chrome, it'd be helpful if you could peek in your Event Viewer,
> and pass along a few crash ID's, (provided that one was generated.)
> Here's how to locate the ID:
> 1. Click Start and select "Run."
> 2. Type "eventvwr" (without quotes) and press Enter. Event Viewer will
> open.
> 3. Double click the "Application" tree to expand it.
> 4. Click the "Source" column on the right and scroll down the list
> looking for events named "Chrome."
> 5. Double click the entry to see its details. (Look at the timestamp
> to find recent crash events. If we're lucky, it will contain a crash
> ID).
> 6. Paste the crash ID into this thread with your O/S and version of
> Chrome.
> Thanks very much for helping us get to the bottom of this issue!
> Ben
> On Oct 3, 12:34 am, element1 wrote:
> > It's happening on all our office/domain machines also.
> > I suspect it was blocked centrally somehow.
> > On Oct 2, 7:50 pm, Toby-Wan wrote:
> > > I forgot in my earlier post to mention that I'm seeing this same
> > > problem on all of the computers here in my office that are hooked up
> > > to the domain. Not sure, but might have something to do with it.
> > > Anyone else with the problem either always or sometimes connected to a
> > > domain?
> > > On Oct 1, 7:25 pm, Google Guide wrote:
> > > > Hi StealthWind,
> > > > It's a tough situation -- if you use Google Chrome without the
> > > > sandbox, you're opening yourself up to some heavy security risks. If
> > > > you don't turn off the sandbox, you have no choice but to use another
> > > > browser for the time being. I know it sounds strange for someone on
> > > > the Google Chrome team to recommend you use another browser in this
> > > > case, but I don't want your system to be compromised.
> > > > Have I shared this link yet? It's the pages in the Google Chrome comic
> > > > book that describe the sandbox.
> > > > Naturally, this is a top area of focus for me -- we've got to find out
> > > > what's causing these renderer crashes. It seems that software conflict
> > > > is a major suspect, so please share with us what other processes are
> > > > running on your system and we'll see if there are any commonalities.
> > > > Thanks for understanding,
> > > > Simon
> > > > On Sep 30, 9:27 pm, StealthWind wrote:
> > > > > But then how are we supposed to use Google Chrome without the --no-
> > > > > sandbox option since we can't even load a single page without it?
> > > > > Thanks.
> > > > > On Oct 1, 1:55 am, Google Guide 2 wrote:
> > > > > > Hi Sridhar,
> > > > > > "Aw Snap" error on every page points to a renderer crash -- why
> > > > > > exactly the renderer crashes is the mystery.
> > > > > > Let's try to collect as much system information as possible to see if
> > > > > > there are commonalities among those whose renderer crashes.
> > > > > > Toby-wan, thanks so much for the detail. I'll pass it around and see
> > > > > > what we can do with it.
> > > > > > Crltn, I understand how frustrating it can be to be told not to use a
> > > > > > workaround that seems to work so effectively. Since turning off
> > > > > > sandbox opens you to security risks, it's safer to not risk it.
> > > > > > Thanks everyone for your patience with these crashes -- hopefully
> > > > > > we'll find more leads on specific issues that cause renderer crashes.
> > > > > > Simon
> > > > > > On Sep 23, 9:24 pm, Crltn wrote:
> > > > > > > Greetings Simon,
> > > > > > > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > > > > > > able to get Chrome to run using --no-sandbox; now I read don't use the
> > > > > > > --no-sandbox argument. So what am I to use???
> > > > > > > Crltn
> > > > > > > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > > > > > > Hi all,
> > > > > > > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > > > > > > have found that turning off the sandbox resolves the issue.
> > > > > > > > However, please do not use the --no-sandbox option.
> > > > > > > > This option disables the low-privilege sandbox for showing web pages,
> > > > > > > > which leaves your
> > > > > > > > computer more vulnerable to flaws or security exploits on those pages.
> > > > > > > > It is intended for testing purposes only.
> > > > > > > > It's very important that Google Chrome is not run without the sandbox,
> > > > > > > > because of the inherent security vulnerabilities in that mode. We're
> > > > > > > > working very hard to fix the issues some of you are seeing, but in the
> > > > > > > > meantime, please don't use the --no-sandbox option.
The exactly same problem as described by "Zoggle" below, happened on
my machine too.
Always "waiting ....." on the bottom of chrome.
no source named "chrome" show up in eventvwr window. and there are
many fail i/o, but not sure whether it is related to chrome or not.
But I found out some "Application error" in event viewer, hope this
could help google team to solve this problem.
the following is the information I got from event viewer:
> For those of you experiencing the "Aww Snap" >> Renderer crash in
> Google Chrome, it'd be helpful if you could peek in your Event Viewer,
> and pass along a few crash ID's, (provided that one was generated.)
> Here's how to locate the ID:
> 1. Click Start and select "Run."
> 2. Type "eventvwr" (without quotes) and press Enter. Event Viewer will
> open.
> 3. Double click the "Application" tree to expand it.
> 4. Click the "Source" column on the right and scroll down the list
> looking for events named "Chrome."
> 5. Double click the entry to see its details. (Look at the timestamp
> to find recent crash events. If we're lucky, it will contain a crash
> ID).
> 6. Paste the crash ID into this thread with your O/S and version of
> Chrome.
> Thanks very much for helping us get to the bottom of this issue!
> Ben
> On Oct 3, 12:34 am, element1 wrote:
> > It's happening on all our office/domain machines also.
> > I suspect it was blocked centrally somehow.
> > On Oct 2, 7:50 pm, Toby-Wan wrote:
> > > I forgot in my earlier post to mention that I'm seeing this same
> > > problem on all of the computers here in my office that are hooked up
> > > to the domain. Not sure, but might have something to do with it.
> > > Anyone else with the problem either always or sometimes connected to a
> > > domain?
> > > On Oct 1, 7:25 pm, Google Guide wrote:
> > > > Hi StealthWind,
> > > > It's a tough situation -- if you use Google Chrome without the
> > > > sandbox, you're opening yourself up to some heavy security risks. If
> > > > you don't turn off the sandbox, you have no choice but to use another
> > > > browser for the time being. I know it sounds strange for someone on
> > > > the Google Chrome team to recommend you use another browser in this
> > > > case, but I don't want your system to be compromised.
> > > > Have I shared this link yet? It's the pages in the Google Chrome comic
> > > > book that describe the sandbox.
> > > > Naturally, this is a top area of focus for me -- we've got to find out
> > > > what's causing these renderer crashes. It seems that software conflict
> > > > is a major suspect, so please share with us what other processes are
> > > > running on your system and we'll see if there are any commonalities.
> > > > Thanks for understanding,
> > > > Simon
> > > > On Sep 30, 9:27 pm, StealthWind wrote:
> > > > > But then how are we supposed to use Google Chrome without the --no-
> > > > > sandbox option since we can't even load a single page without it?
> > > > > Thanks.
> > > > > On Oct 1, 1:55 am, Google Guide 2 wrote:
> > > > > > Hi Sridhar,
> > > > > > "Aw Snap" error on every page points to a renderer crash -- why
> > > > > > exactly the renderer crashes is the mystery.
> > > > > > Let's try to collect as much system information as possible to see if
> > > > > > there are commonalities among those whose renderer crashes.
> > > > > > Toby-wan, thanks so much for the detail. I'll pass it around and see
> > > > > > what we can do with it.
> > > > > > Crltn, I understand how frustrating it can be to be told not to use a
> > > > > > workaround that seems to work so effectively. Since turning off
> > > > > > sandbox opens you to security risks, it's safer to not risk it.
> > > > > > Thanks everyone for your patience with these crashes -- hopefully
> > > > > > we'll find more leads on specific issues that cause renderer crashes.
> > > > > > Simon
> > > > > > On Sep 23, 9:24 pm, Crltn wrote:
> > > > > > > Greetings Simon,
> > > > > > > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > > > > > > able to get Chrome to run using --no-sandbox; now I read don't use the
> > > > > > > --no-sandbox argument. So what am I to use???
> > > > > > > Crltn
> > > > > > > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > > > > > > Hi all,
> > > > > > > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > > > > > > have found that turning off the sandbox resolves the issue.
> > > > > > > > However, please do not use the --no-sandbox option.
> > > > > > > > This option disables the low-privilege sandbox for showing web pages,
> > > > > > > > which leaves your
> > > > > > > > computer more vulnerable to flaws or security exploits on those pages.
> > > > > > > > It is intended for testing purposes only.
> > > > > > > > It's very important that Google Chrome is not run without the sandbox,
> > > > > > > > because of the inherent security vulnerabilities in that mode. We're
> > > > > > > > working very hard to fix the issues some of you are seeing, but in the
> > > > > > > > meantime, please don't use the --no-sandbox option.
Is there fix for this issue.
It seems that on my laptop, if and only if I use the "--no-sandbox
option" I am able to get to the internet.
I am wondering if there is any updates
The build that I use is
Official Build 2200
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13
(KHTML, like Gecko) Chrome/0.2.149.30 Safari/525.13
> For users with 0xc00000005 errors, as well as a few other errors, some
> have found that turning off the sandbox resolves the issue.
> However, please do not use the --no-sandbox option.
> This option disables the low-privilege sandbox for showing web pages,
> which leaves your
> computer more vulnerable to flaws or security exploits on those pages.
> It is intended for testing purposes only.
> It's very important that Google Chrome is not run without the sandbox,
> because of the inherent security vulnerabilities in that mode. We're
> working very hard to fix the issues some of you are seeing, but in the
> meantime, please don't use the --no-sandbox option.
I could find several crashes, all with the same description (naturally
the time stamp differs):
Event Type: Information
Event Source: Chrome
Event Category: None
Event ID: 2
Date: 10/23/2008
Time: 23:01:02
User: [...]
Computer: [...]
Description:
The description for Event ID ( 2 ) in Source ( Chrome ) cannot be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Chrome. Crash uploaded.
Id=87d64891a74e5dbb.
Other similar entries with ID:
Id=beb187f04b046066
Id=c43daabf3ed4b095
Id=6f86327e5bac0c3
Id=e03a6cd2af17f79d
Id=2e39ff72ac96d25b
I'm using a corporate laptop. Windows XP SP2, 2GB RAM, McAfee
VirusScan Enterprise + Anti-Spyware Module 8.0.
I've been using Chrome sonce it was launched, and I need to confess I
really like using it. It has been working without any problems, but
after a Windows XP blue screen, I started getting thos "Aw, Snap!"
message to any tab I open. I tried to uninstall and reinstall the
browser, but the same problem persist. The "sandbox" option allows the
browser to work properly.
> For those of you experiencing the "Aww Snap" >> Renderer crash in
> Google Chrome, it'd be helpful if you could peek in your Event Viewer,
> and pass along a few crash ID's, (provided that one was generated.)
> Here's how to locate the ID:
> 1. Click Start and select "Run."
> 2. Type "eventvwr" (without quotes) and press Enter. Event Viewer will
> open.
> 3. Double click the "Application" tree to expand it.
> 4. Click the "Source" column on the right and scroll down the list
> looking for events named "Chrome."
> 5. Double click the entry to see its details. (Look at the timestamp
> to find recent crash events. If we're lucky, it will contain a crash
> ID).
> 6. Paste the crash ID into this thread with your O/S and version of
> Chrome.
> Thanks very much for helping us get to the bottom of this issue!
> Ben
> On Oct 3, 12:34 am, element1 wrote:
> > It's happening on all our office/domain machines also.
> > I suspect it was blocked centrally somehow.
> > On Oct 2, 7:50 pm, Toby-Wan wrote:
> > > I forgot in my earlier post to mention that I'm seeing this same
> > > problem on all of the computers here in my office that are hooked up
> > > to the domain. Not sure, but might have something to do with it.
> > > Anyone else with the problem either always or sometimes connected to a
> > > domain?
> > > On Oct 1, 7:25 pm, Google Guide wrote:
> > > > Hi StealthWind,
> > > > It's a tough situation -- if you use Google Chrome without the
> > > > sandbox, you're opening yourself up to some heavy security risks. If
> > > > you don't turn off the sandbox, you have no choice but to use another
> > > > browser for the time being. I know it sounds strange for someone on
> > > > the Google Chrome team to recommend you use another browser in this
> > > > case, but I don't want your system to be compromised.
> > > > Have I shared this link yet? It's the pages in the Google Chrome comic
> > > > book that describe the sandbox.
> > > > Naturally, this is a top area of focus for me -- we've got to find out
> > > > what's causing these renderer crashes. It seems that software conflict
> > > > is a major suspect, so please share with us what other processes are
> > > > running on your system and we'll see if there are any commonalities.
> > > > Thanks for understanding,
> > > > Simon
> > > > On Sep 30, 9:27 pm, StealthWind wrote:
> > > > > But then how are we supposed to use Google Chrome without the --no-
> > > > > sandbox option since we can't even load a single page without it?
> > > > > Thanks.
> > > > > On Oct 1, 1:55 am, Google Guide 2 wrote:
> > > > > > Hi Sridhar,
> > > > > > "Aw Snap" error on every page points to a renderer crash -- why
> > > > > > exactly the renderer crashes is the mystery.
> > > > > > Let's try to collect as much system information as possible to see if
> > > > > > there are commonalities among those whose renderer crashes.
> > > > > > Toby-wan, thanks so much for the detail. I'll pass it around and see
> > > > > > what we can do with it.
> > > > > > Crltn, I understand how frustrating it can be to be told not to use a
> > > > > > workaround that seems to work so effectively. Since turning off
> > > > > > sandbox opens you to security risks, it's safer to not risk it.
> > > > > > Thanks everyone for your patience with these crashes -- hopefully
> > > > > > we'll find more leads on specific issues that cause renderer crashes.
> > > > > > Simon
> > > > > > On Sep 23, 9:24 pm, Crltn wrote:
> > > > > > > Greetings Simon,
> > > > > > > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > > > > > > able to get Chrome to run using --no-sandbox; now I read don't use the
> > > > > > > --no-sandbox argument. So what am I to use???
> > > > > > > Crltn
> > > > > > > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > > > > > > Hi all,
> > > > > > > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > > > > > > have found that turning off the sandbox resolves the issue.
> > > > > > > > However, please do not use the --no-sandbox option.
> > > > > > > > This option disables the low-privilege sandbox for showing web pages,
> > > > > > > > which leaves your
> > > > > > > > computer more vulnerable to flaws or security exploits on those pages.
> > > > > > > > It is intended for testing purposes only.
> > > > > > > > It's very important that Google Chrome is not run without the sandbox,
> > > > > > > > because of the inherent security vulnerabilities in that mode. We're
> > > > > > > > working very hard to fix the issues some of you are seeing, but in the
> > > > > > > > meantime, please don't use the --no-sandbox option.
We've made some fixes to the latest version that should resolve this
problem. If you haven't been updated to version 0.3.154.9 yet, you can
update your version of Google Chrome by following the steps outlined
here:
If you've updated but still have 'Aw Snap' on every page, please let
us know on our new Google Chrome Help Forum. We're discussing this
issue on this thread:
> I could find several crashes, all with the same description (naturally
> the time stamp differs):
> Event Type: Information
> Event Source: Chrome
> Event Category: None
> Event ID: 2
> Date: 10/23/2008
> Time: 23:01:02
> User: [...]
> Computer: [...]
> Description:
> The description for Event ID ( 2 ) in Source ( Chrome ) cannot be
> found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE= flag to retrieve this
> description; see Help and Support for details. The following
> information is part of the event: Chrome. Crash uploaded.
> Id=87d64891a74e5dbb.
> Other similar entries with ID:
> Id=beb187f04b046066
> Id=c43daabf3ed4b095
> Id=6f86327e5bac0c3
> Id=e03a6cd2af17f79d
> Id=2e39ff72ac96d25b
> I'm using a corporate laptop. Windows XP SP2, 2GB RAM, McAfee
> VirusScan Enterprise + Anti-Spyware Module 8.0.
> I've been using Chrome sonce it was launched, and I need to confess I
> really like using it. It has been working without any problems, but
> after a Windows XP blue screen, I started getting thos "Aw, Snap!"
> message to any tab I open. I tried to uninstall and reinstall the
> browser, but the same problem persist. The "sandbox" option allows the
> browser to work properly.
> Do you have any updates on this?
> Regards, Nuno
> On Oct 3, 6:17 pm, Google Guide wrote:
> > For those of you experiencing the "Aww Snap" >> Renderer crash in
> > Google Chrome, it'd be helpful if you could peek in your Event Viewer,
> > and pass along a few crash ID's, (provided that one was generated.)
> > Here's how to locate the ID:
> > 1. Click Start and select "Run."
> > 2. Type "eventvwr" (without quotes) and press Enter. Event Viewer will
> > open.
> > 3. Double click the "Application" tree to expand it.
> > 4. Click the "Source" column on the right and scroll down the list
> > looking for events named "Chrome."
> > 5. Double click the entry to see its details. (Look at the timestamp
> > to find recent crash events. If we're lucky, it will contain a crash
> > ID).
> > 6. Paste the crash ID into this thread with your O/S and version of
> > Chrome.
> > Thanks very much for helping us get to the bottom of this issue!
> > Ben
> > On Oct 3, 12:34 am, element1 wrote:
> > > It's happening on all our office/domain machines also.
> > > I suspect it was blocked centrally somehow.
> > > On Oct 2, 7:50 pm, Toby-Wan wrote:
> > > > I forgot in my earlier post to mention that I'm seeing this same
> > > > problem on all of the computers here in my office that are hooked up
> > > > to the domain. Not sure, but might have something to do with it.
> > > > Anyone else with the problem either always or sometimes connected to a
> > > > domain?
> > > > On Oct 1, 7:25 pm, Google Guide wrote:
> > > > > Hi StealthWind,
> > > > > It's a tough situation -- if you use Google Chrome without the
> > > > > sandbox, you're opening yourself up to some heavy security risks. If
> > > > > you don't turn off the sandbox, you have no choice but to use another
> > > > > browser for the time being. I know it sounds strange for someone on
> > > > > the Google Chrome team to recommend you use another browser in this
> > > > > case, but I don't want your system to be compromised.
> > > > > Have I shared this link yet? It's the pages in the Google Chrome comic
> > > > > book that describe the sandbox.
> > > > > Naturally, this is a top area of focus for me -- we've got to find out
> > > > > what's causing these renderer crashes. It seems that software conflict
> > > > > is a major suspect, so please share with us what other processes are
> > > > > running on your system and we'll see if there are any commonalities.
> > > > > Thanks for understanding,
> > > > > Simon
> > > > > On Sep 30, 9:27 pm, StealthWind wrote:
> > > > > > But then how are we supposed to use Google Chrome without the --no-
> > > > > > sandbox option since we can't even load a single page without it?
> > > > > > Thanks.
> > > > > > On Oct 1, 1:55 am, Google Guide 2 wrote:
> > > > > > > Hi Sridhar,
> > > > > > > "Aw Snap" error on every page points to a renderer crash -- why
> > > > > > > exactly the renderer crashes is the mystery.
> > > > > > > Let's try to collect as much system information as possible to see if
> > > > > > > there are commonalities among those whose renderer crashes.
> > > > > > > Toby-wan, thanks so much for the detail. I'll pass it around and see
> > > > > > > what we can do with it.
> > > > > > > Crltn, I understand how frustrating it can be to be told not to use a
> > > > > > > workaround that seems to work so effectively. Since turning off
> > > > > > > sandbox opens you to security risks, it's safer to not risk it.
> > > > > > > Thanks everyone for your patience with these crashes -- hopefully
> > > > > > > we'll find more leads on specific issues that cause renderer crashes.
> > > > > > > Simon
> > > > > > > On Sep 23, 9:24 pm, Crltn wrote:
> > > > > > > > Greetings Simon,
> > > > > > > > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > > > > > > > able to get Chrome to run using --no-sandbox; now I read don't use the
> > > > > > > > --no-sandbox argument. So what am I to use???
> > > > > > > > Crltn
> > > > > > > > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > > > > > > > Hi all,
> > > > > > > > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > > > > > > > have found that turning off the sandbox resolves the issue.
> > > > > > > > > However, please do not use the --no-sandbox option.
> > > > > > > > > This option disables the low-privilege sandbox for showing web pages,
> > > > > > > > > which leaves your
> > > > > > > > > computer more vulnerable to flaws or security exploits on those pages.
> > > > > > > > > It is intended for testing purposes only.
> > > > > > > > > It's very important that Google Chrome is not run without the sandbox,
> > > > > > > > > because of the inherent security vulnerabilities in that mode. We're
> > > > > > > > > working very hard to fix the issues some of you are seeing, but in the
> > > > > > > > > meantime, please don't use the --no-sandbox option.
> We've made some fixes to the latest version that should resolve this
> problem. If you haven't been updated to version 0.3.154.9 yet, you can
> update your version of Google Chrome by following the steps outlined
> here:
> If you've updated but still have 'Aw Snap' on every page, please let
> us know on our new Google Chrome Help Forum. We're discussing this
> issue on this thread:
> Thanks -- we'll retire this help group soon, so make sure to post to
> our new thread with any continuing issues.
> - Maggie
> On Oct 24, 4:11 pm, NunoG wrote:
> > Hi Ben,
> > I could find several crashes, all with the same description (naturally
> > the time stamp differs):
> > Event Type: Information
> > Event Source: Chrome
> > Event Category: None
> > Event ID: 2
> > Date: 10/23/2008
> > Time: 23:01:02
> > User: [...]
> > Computer: [...]
> > Description:
> > The description for Event ID ( 2 ) in Source ( Chrome ) cannot be
> > found. The local computer may not have the necessary registry
> > information or message DLL files to display messages from a remote
> > computer. You may be able to use the /AUXSOURCE= flag to retrieve this
> > description; see Help and Support for details. The following
> > information is part of the event: Chrome. Crash uploaded.
> > Id=87d64891a74e5dbb.
> > Other similar entries with ID:
> > Id=beb187f04b046066
> > Id=c43daabf3ed4b095
> > Id=6f86327e5bac0c3
> > Id=e03a6cd2af17f79d
> > Id=2e39ff72ac96d25b
> > I'm using a corporate laptop. Windows XP SP2, 2GB RAM, McAfee
> > VirusScan Enterprise + Anti-Spyware Module 8.0.
> > I've been using Chrome sonce it was launched, and I need to confess I
> > really like using it. It has been working without any problems, but
> > after a Windows XP blue screen, I started getting thos "Aw, Snap!"
> > message to any tab I open. I tried to uninstall and reinstall the
> > browser, but the same problem persist. The "sandbox" option allows the
> > browser to work properly.
> > Do you have any updates on this?
> > Regards, Nuno
> > On Oct 3, 6:17 pm, Google Guide wrote:
> > > For those of you experiencing the "Aww Snap" >> Renderer crash in
> > > Google Chrome, it'd be helpful if you could peek in your Event Viewer,
> > > and pass along a few crash ID's, (provided that one was generated.)
> > > Here's how to locate the ID:
> > > 1. Click Start and select "Run."
> > > 2. Type "eventvwr" (without quotes) and press Enter. Event Viewer will
> > > open.
> > > 3. Double click the "Application" tree to expand it.
> > > 4. Click the "Source" column on the right and scroll down the list
> > > looking for events named "Chrome."
> > > 5. Double click the entry to see its details. (Look at the timestamp
> > > to find recent crash events. If we're lucky, it will contain a crash
> > > ID).
> > > 6. Paste the crash ID into this thread with your O/S and version of
> > > Chrome.
> > > Thanks very much for helping us get to the bottom of this issue!
> > > Ben
> > > On Oct 3, 12:34 am, element1 wrote:
> > > > It's happening on all our office/domain machines also.
> > > > I suspect it was blocked centrally somehow.
> > > > On Oct 2, 7:50 pm, Toby-Wan wrote:
> > > > > I forgot in my earlier post to mention that I'm seeing this same
> > > > > problem on all of the computers here in my office that are hooked up
> > > > > to the domain. Not sure, but might have something to do with it.
> > > > > Anyone else with the problem either always or sometimes connected to a
> > > > > domain?
> > > > > On Oct 1, 7:25 pm, Google Guide wrote:
> > > > > > Hi StealthWind,
> > > > > > It's a tough situation -- if you use Google Chrome without the
> > > > > > sandbox, you're opening yourself up to some heavy security risks. If
> > > > > > you don't turn off the sandbox, you have no choice but to use another
> > > > > > browser for the time being. I know it sounds strange for someone on
> > > > > > the Google Chrome team to recommend you use another browser in this
> > > > > > case, but I don't want your system to be compromised.
> > > > > > Have I shared this link yet? It's the pages in the Google Chrome comic
> > > > > > book that describe the sandbox.
> > > > > > Naturally, this is a top area of focus for me -- we've got to find out
> > > > > > what's causing these renderer crashes. It seems that software conflict
> > > > > > is a major suspect, so please share with us what other processes are
> > > > > > running on your system and we'll see if there are any commonalities.
> > > > > > > But then how are we supposed to use Google Chrome without the --no-
> > > > > > > sandbox option since we can't even load a single page without it?
> > > > > > > Thanks.
> > > > > > > On Oct 1, 1:55 am, Google Guide 2 wrote:
> > > > > > > > Hi Sridhar,
> > > > > > > > "Aw Snap" error on every page points to a renderer crash -- why
> > > > > > > > exactly the renderer crashes is the mystery.
> > > > > > > > Let's try to collect as much system information as possible to see if
> > > > > > > > there are commonalities among those whose renderer crashes.
> > > > > > > > Toby-wan, thanks so much for the detail. I'll pass it around and see
> > > > > > > > what we can do with it.
> > > > > > > > Crltn, I understand how frustrating it can be to be told not to use a
> > > > > > > > workaround that seems to work so effectively. Since turning off
> > > > > > > > sandbox opens you to security risks, it's safer to not risk it.
> > > > > > > > Thanks everyone for your patience with these crashes -- hopefully
> > > > > > > > we'll find more leads on specific issues that cause renderer crashes.
> > > > > > > > Simon
> > > > > > > > On Sep 23, 9:24 pm, Crltn wrote:
> > > > > > > > > Greetings Simon,
> > > > > > > > > I posted some history in '0xc0000022 issue'; after 8 tries was finally
> > > > > > > > > able to get Chrome to run using --no-sandbox; now I read don't use the
> > > > > > > > > --no-sandbox argument. So what am I to use???
> > > > > > > > > Crltn
> > > > > > > > > On Sep 10, 8:32 am, Google Guide 2 wrote:
> > > > > > > > > > Hi all,
> > > > > > > > > > For users with 0xc00000005 errors, as well as a few other errors, some
> > > > > > > > > > have found that turning off the sandbox resolves the issue.
> > > > > > > > > > However, please do not use the --no-sandbox option.
> > > > > > > > > > This option disables the low-privilege sandbox for showing web pages,
> > > > > > > > > > which leaves your
> > > > > > > > > > computer more vulnerable to flaws or security exploits on those pages.
> > > > > > > > > > It is intended for testing purposes only.
> > > > > > > > > > It's very important that Google Chrome is not run without the sandbox,
> > > > > > > > > > because of the inherent security vulnerabilities in that mode. We're
> > > > > > > > > > working very hard to fix the issues some of you are seeing, but in the
> > > > > > > > > > meantime, please don't use the --no-sandbox option.
