Google Chroming, but Missing the Point
nazham.com and dirn.name got me all excited to try out Google’s new web browser, Chrome.
Installation was indeed very fast. But then:
Oh no. Apparently everyone who is using Symantec Endpoint Protection is facing the exact same issue. I tried to configure SEP to ignore chrome.exe, but in vain. So now I have to run chrome.exe with the --no-sandbox flag, which is rather missing the point, for the biggest advantage of Google Chrome is that each tab runs as its own process.
But still, I’m happy enough that I’m getting to try out Google Chrome. It’s very fast, especially for Gmail and Google Reader, apparently due to its multithreaded architecture.
Interestingly Google Chrome is installed in
C:\Documents and Settings\<username>\Local Settings\Application Data\Google\Chrome\Application
and not in
C:\Program Files
as is usually the case.
Update 4 September 2008
The --no-sandbox option does not disable the one-process-per-tab feature, as I had mentioned above. It disables the sandbox protection that keeps the system safe from problems in web sites’ HTML and JavaScript. Please see my next post.
3 Responses to “Google Chroming, but Missing the Point”
1 mang0 3 September 2008 @ 7:41 pm
Web browser also need installation? Hhmm, let me try.
2 dirn 3 September 2008 @ 7:48 pm
at least you managed to install it successfully and tested it :D.
3 Google Chrome: My Findings So Far | romantika.name 3 September 2008 @ 9:52 pm
[…] with Symantec Endpoint Protection: ill-fated users of SEP like Rizal will for now have to make peace with the fact that they must use the –no-sandbox flag when […]
Comments: