Multithreading – why is Google Chrome renderer multiprocessing rather than multithreading?
•
Java
Every time I load browser tags in chrome on my Mac, the application forks out to another process This seems to work differently from Firefox or safari What is the reason why Google is far away from multithreading in this case? The problem to be solved here (rendering multiple pages at once seems to me to be the main candidate for multithreading, or?
Solution
Running each page (or tab) in a separate process allows chrome to provide higher security to prevent page rendering errors and browser plug-ins running in the process Basically, if a page crashes, it won't affect other tabs Instead, you get an "aw snap!" Information
From docs:
The content of this article comes from the network collection of netizens. It is used as a learning reference. The copyright belongs to the original author.
THE END
二维码