Even if Chrome is multi-process it still happens that the whole browser crashes. I use both FF and Chrome on a daily basis and if you ask me about stability, I would say they are the same. I’m not a big fan of Firefox going multi-process, since I don’t see a big benefit and mostly see it as an excuse for bad engineering. That's definitely good news considering that Firefox's excellent memory usage won't inflate because of this feature.Īdditional information about the current implementation, and what's in store for the future, are available on Bill's blog. The overhead is just 10 Megabytes in comparison, and the developers have stated that they may be able to reduce it further. ![]() Memory usage on the other hand is similar to single-process Firefox. This is a work in progress, and the feature will be implemented eventually. If you open the Task Manager, you do not see individual firefox.exe processes for each website that is open in the browser like you see when using Chrome. ![]() Others may not work yet, like developer tools or saving pages to disks.Īs far as addons are concerned, you will notice that some will work without issues, while many won't just yet.įor now, Firefox will continue to use a single content process and not multiple content processes. ![]() We tried to display this Web page, but it is not responding.įor now, basic functionality has been integrated which means that you can use things like navigating, using the url and search bar, context menus, bookmarks and tabs for example.
0 Comments
Leave a Reply. |