maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   Google Browser: Chrome (https://talk.maemo.org/showthread.php?t=23322)

tso 2008-09-02 16:47

Re: Google Browser: Chrome
 
i think browserd is more complex than that.

it seems the window is what holds the current rendered page and data, so that even if browserd dies from a bad script or something else, the different browser windows dont die, except for the one that was connected to whatever it was that made browserd die...

but this is me sitting on the fence, observing the process list...

epage 2008-09-02 17:15

Re: Google Browser: Chrome
 
Quote:

Originally Posted by coffeedrinker (Post 220120)
Well, isn't putting each on in its own process and each one having its own interface essentially just running multiple instances, but under one main window?

I spawn multiple copies of links rather than use one process with several windows. Then when I close that "tab" all the memory is reclaimed and I don't have to worry about any cached pages.

browserd, I think, is just the opposite. It is one rendering engine with the ability to respawn the main window. Closing the window doesn't even have any effect on the browser. Am I understanding this correctly?

Fork is the main way of creating new processes on Linux. When you fork a process, it does not duplicate all of the memory pages but instead marks them as needing to be copied on the next write. If writes never happens or are rare, than very little memory is spent in having two processes. Also on Linux, threads are implemented through processes that share the same memory pages.
http://linux.about.com/od/commands/l/blcmdl2_fork.htm

So in theory, if there are very few changes to the pages of a virgin webkit and that there is little in common between once rendering pages, then the overhead of separate processes would be negligible.

Disclaimer: I do not know details of browserd. I have no clue what benefits it might have by what structure it might use.

iamthewalrus 2008-09-02 17:35

Re: Google Browser: Chrome
 
Quote:

Originally Posted by epage (Post 220133)
Fork is the main way of creating new processes on Linux. When you fork a process, it does not duplicate all of the memory pages but instead marks them as needing to be copied on the next write. If writes never happens or are rare, than very little memory is spent in having two processes. Also on Linux, threads are implemented through processes that share the same memory pages.
http://linux.about.com/od/commands/l/blcmdl2_fork.htm

So in theory, if there are very few changes to the pages of a virgin webkit and that there is little in common between once rendering pages, then the overhead of separate processes would be negligible.

Disclaimer: I do not know details of browserd. I have no clue what benefits it might have by what structure it might use.

I can remember reading that, unlike Linux, in Windows there is a cost to spawning processes. Maybe that's causing the confusion.

Benson 2008-09-02 18:12

Re: Google Browser: Chrome
 
Should be available for download Noon PDT (1900 UTC)!

wjanowski 2008-09-02 18:50

Re: Google Browser: Chrome
 
The download link is back up at http://gears.google.com/chrome, but the "accept and install" link seems broken.

EDIT: The link at http://www.google.com/chrome now seems to be working OK.

lbalogh 2008-09-02 18:58

Re: Google Browser: Chrome
 
http://dl.google.com/update2/installers/ChromeSetup.exe

andrewfblack 2008-09-02 19:02

Re: Google Browser: Chrome
 
First itT post on google chrome!
itT runs faster on this I swear.

Oberon85 2008-09-02 19:05

Re: Google Browser: Chrome
 
second post? darn!! fresh from chrome

Reggie 2008-09-02 19:11

Re: Google Browser: Chrome
 
Quote:

Originally Posted by andrewfblack (Post 220175)
First itT post on google chrome!
itT runs faster on this I swear.

Wow, I agree. Speed is outstanding!

CleverJake 2008-09-02 19:16

Re: Google Browser: Chrome
 
Jesus H tapdancing christ this thing is flying
=D


All times are GMT. The time now is 11:56.

vBulletin® Version 3.8.8