Täna, see küsimuste ja vastuste seanss tuleb meile viisakalt Super-kasutaja, Stowe Exchange'i alamrubriigist, Q & A veebisaitide kogukonnapõhiseks rühmituseks.
Küsimus
Kui te olete huvitatud kõigist nendest, mis näib olevat dubleerivad Chrome'i protsesse, siis ei ole te üksi. SuperUser lugeja PolyShell tõesti tahab saada asjade alt:
In Windows Task Manager it seems that I have multiple Chrome processes running, even though I only have one Chrome window open.
How is this possible? I always thought each open program represented one process.
Kuigi esialgse protsessi üksikprotsessi kroom.exe ülaosa näib hämmastav, on see suurepärane seletus õnne jaoks.
Vastused
Mitu SuperUseri panustajat panid küsimusele vastama. Jeff Atwood pakkus viidet Chrome'i arendusblogile:
You can read the details here:
Google Chrome takes advantage of these properties and puts web apps and plug-ins in separate processes from the browser itself. This means that a rendering engine crash in one web app won’t affect the browser or other web apps. It means the OS can run web apps in parallel to increase their responsiveness, and it means the browser itself won’t lock up if a particular web app or plug-in stops responding. It also means we can run the rendering engine processes in a restrictive sandbox that helps limit the damage if an exploit does occur.
Basically, each tab has one process unless the tabs are from the same domain. The renderer has a process for itself. Each plug-in will have one and so will each extension that is active.
KronoS jagab trikki Chrome'i protsesside uurimiseks, mis on loetletud mõne muu käsitsi Taskuhalduri asemel:
You can see which process does what on:
Menu-> Tools -> Task Manager
Which looks like this:
Don’t forget to read the Chrome introduction comic that covers this among other design decisions.
Kas teil on seletamiseks midagi lisada? Helistage kommentaarides. Kas soovite lugeda rohkem vastuseid teistelt tech-savvy Stack Exchange'i kasutajatelt? Tutvu täieliku arutelu teemaga siit.
