ok, we can rule out the domain issue. pls note that the Chrome program did not crash to have an event in system log, but to display the "Aw, Snap!" page, it should be considered as a crashed page I guess? Well, let's look at the AV issue, I have Office Scan installed on my machine, and I tried to stop its service, but I still get the "Aw, Snap!" page. I'll uninstall the AV to see if it will help. There may be another possibility that some software policies which are applied by domain controller may cause the error page. If you can show me on what conditions an "Aw, Snap!" page will be displayed, I can try to check the items. And I have Chrome diagnostic utility checked my system, but can't find any useful information. BTW, I tested more machines, the problem exists on XP pro en/cn & SP2/ SP3 in the same domain. I like the Chrome browser, but it's a pity that I can't use it at work. Wish you guys can make it a better one. thx!
On Sep 17, 9:43 pm, Clint <[EMAIL PROTECTED]> wrote: > indeed. Running on multiple AD authenticated domain machines here > including 3 domain controllers. > > On Sep 17, 4:45 am, deanm <[EMAIL PROTECTED]> wrote: > > > I don't think this has anything to do with the fact that your machine > > is domain joined. We have lots of people running Chromium on domain > > joined machines. > > > If I had to guess, I would think it's something related to anti- > > virus? If you could give us more details that would help. Also, if > > you opted into sending crash reports, we should have some crash dumps, > > if you could send us the crash ids (they are in the eventlog). > > > On Sep 17, 10:13 am, Marble <[EMAIL PROTECTED]> wrote: > > > > Hi Brett, > > > I mean PCs that are added to a company domain rather than a workgroup. > > > Every time I open Chrome, it will show an "Aw, Snap!" page, and > > > there's instruction shows "Something went wrong while displaying this > > > webpage.To continue, press Reload or go to anothe page.". I tried to > > > "reload" the page, won't work, and I tried "another page" such as > > > "about:blank" & "about:memory", still the same error. It also happened > > > on another machine which is in the same domain. Did you guys ever test > > > Chrome in a domain machine? It doesn't seem to be a single case, I'll > > > try to test Chrome on more machines in the same domain. > > > thx! > > > > On Sep 17, 11:05 am, Brett Wilson <[EMAIL PROTECTED]> wrote: > > > > > I don't know what a "domain PC" is. Can you elaborate? > > > > > Brett --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
