This message-passing mechanism has been in place since Firefox 4. The result is a design that can be quite a bit more complicated than in single-process Firefox. To ensure that the user interface doesn't hang and remains responsive, those messages are asynchronous-the message sender doesn't wait for the message to actually be received. Every such access has to be passed through a message-passing interface that connects the two processes. With multiple processes, that's no longer possible: the add-ins and user interface exist in one process, the page structure in a separate one. In single process Firefox, add-ins and the browser user interface itself can directly access the page structure. Substantial work has been done to make Firefox work with multiple processes. The Firefox developer tools, for example, are non-functional. While basic browsing and some add-ons work already, others don't.
The organization still has a lot of work to do before multiprocess support is ready for prime time. Where those browsers will create a whole bunch of processes (generally around one per tab), Firefox Nightly creates two: one for the browser window and chrome itself, another for all the tab content. Currently, this is still quite limited when compared to Internet Explorer and Chrome. Nightly builds of Firefox can now be used with multiple processes. Work on Electrolysis resumed in January this year, and Mozilla developers have started to talk about it in detail.
4K VIDEO DOWNLOADER PARSING FOREVER FULL
The full Electrolysis project was put on hold just over two years ago. It does have a limited multiprocess design, as it can run plugins in their own process, but everything else is run in a single process, running with the full permissions of the user. It's now late 2013, and Firefox still isn't a multiprocess browser. In 2009, Mozilla announced the Electrolysis project, which was to bring this kind of multiprocess design to Firefox. It also means that they're much more tolerant of crash bugs a bug will bring down an individual tab, but shouldn't, in general, bring down the browser as a whole. This allows them to run the dangerous parts-the parts exposed to malicious scripts and exploitative HTML-in a sandbox with reduced permissions, making it harder for browser flaws to be turned into system compromises. They separate the task of parsing and rendering Web pages from the job of drawing the browser on-screen, saving downloaded files, creating network connections, and so on. Internet Explorer and Chrome both use a multiprocess architecture to enhance stability and security.
0 kommentar(er)
