Google Chrome

Meh.

Despite that it is from 'aren't we so young and funky and ace' Google, I feel this won't actually take off as well as they hope. I don't know why, it is just a feeling. Look how long it has taken Firefox to claw out 10% or so of the browser base, this doesn't seem to offer enough to challenge even Opera at the moment.

Maybe in 10 years but that is an awful long time on the interwebnet.

I certainly won't be diluting the purity of my Mac with it, that's for sure. ;)
 
Ulfhedjinn said:
Not being funny but I just got it to run 11 processes, make sure you've not got them sorted by memory usage or something (sort by name or description so they're all together).

29mx9pu.png
Click to expand...

Couldn't get mine to open more than 8. Maybe I need to open more! But if you look on the about:memory page you can see it seems to assign more than one tab to a process...

Definately not making this up :) It is not process-per-tab like Google have been saying.

Open up 25 tabs or so with a web page on each. Then kill one of the chrome.exe processes (not the parent one). Now watch as several of your tabs turn to dust :D

I wonder then how clever their "sandboxing" is... and whether this opens up the potential for cross-page security vulnerabilities that are enclosed within the same process i.e. sandbox.
 
AJUK said:
Meh.

Despite that it is from 'aren't we so young and funky and ace' Google, I feel this won't actually take off as well as they hope. I don't know why, it is just a feeling. Look how long it has taken Firefox to claw out 10% or so of the browser base, this doesn't seem to offer enough to challenge even Opera at the moment.

Maybe in 10 years but that is an awful long time on the interwebnet.

I certainly won't be diluting the purity of my Mac with it, that's for sure. ;)
Click to expand...
I tend to agree. Google should stick to what they know best... which is Javascript, D/HTML, AJAX and such like. Browsers written in C++ with the main bits cobled together from a bunch of third party components is not what they should be getting involved in IMO.

I also really don't think the whole "Whoops an error occured! Sha-zam! Damn we're cool and hip!" type of GUI is what people want in their lives.
 
The only time it's putting multiple tabs in the same process for me is if I click 'duplicate tab'. If I manually open a new tab it always get's its own process... 19 processes running at the moment here.

I like its minimalistic look a lot, wish you could move the main tool bar elements around though. I'd much prefer the bookmarks bit on the left hand side.
 
Just tried, but I'm only getting 6.

And all the links opened from the same tab went into the same process. Will keep messing around and see what happens.
 
Very fast and some nice features. However, the extra speed is nto worth loss of plugins that firefox has to offer atm plus the style sucks :( For what it is it is good and i hope it matures well and promptly.
 
NathanE said:
Couldn't get mine to open more than 8. Maybe I need to open more! But if you look on the about:memory page you can see it seems to assign more than one tab to a process...

Definately not making this up :) It is not process-per-tab like Google have been saying.

Open up 25 tabs or so with a web page on each. Then kill one of the chrome.exe processes (not the parent one). Now watch as several of your tabs turn to dust :D

I wonder then how clever their "sandboxing" is... and whether this opens up the potential for cross-page security vulnerabilities that are enclosed within the same process i.e. sandbox.
Click to expand...

I dont think your looking at the right task manager..
googlerg1.jpg
 
You must log in or register to reply here.
Back
Top Bottom