Live data from Hacker News

Update on Multi-Process Firefox

blog.mozilla.org

81–90 of 175 posts

Re: Update on Multi-Process Firefox

#81
post #12

It would be really nice if the addons/extensions page showed which addons were listed as compatible and which weren't. I might thus make a decision to disable/delete an addon or two that were blocking me from using multiprocess firefox. As it is, I have no idea if my firefox is using multiprocess at all. All I know is that I use a lot of addons and I'm probably not, then, using multiprocess.

You can figure out what add-ons are compatible by cross-referencing http://www.arewee10syet.com/

Seems the only addon I use that isn't compatible is "Disable Ctrl-Q Shortcut". It's an addon I really don't want to get rid of, there have been many cases in the past where I've accidentally pressed ctrl+q instead of ctrl+w, and had Firefox quit on me..

Edit: The page for the addon has a comment saying it does work with multiprocess, so I just forced it on. I'm on Linux, and I don't know of an about:config key to disable ctrl+q

Re: Update on Multi-Process Firefox

#82

Is this done in Chrome as early as 8 years ago? https://blog.chromium.org/2008/09/multi-process-architecture...

You mean what was done in IE8 six months before Chrome? https://blogs.msdn.microsoft.com/ie/2008/03/11/ie8-and-loose... More seriously—it's somewhat sad to see Chrome get all the credit for this, when it's undoubtedly the case that both IE and Chrome were working on this at the same time.

If anything we should give the IE guys extra credit, I doubt the code base was pleasant to work with.

Re: Update on Multi-Process Firefox

#83
So now Firefox will become much slower due to per tab process overhead, just like Chrome, will pollute the task list with processes, and lose the enormous benefits of it's fantastic extension model, all for some intangible security benefits?

I've almost never had a security issue or crash on Firefox with a hundred tabs and maybe fifty extensions, it's still faster than chrome with 10 tabs.

Re: Update on Multi-Process Firefox

#84
post #12

Earlier quoted context omitted.

You can figure out what add-ons are compatible by cross-referencing http://www.arewee10syet.com/

Seems the only addon I use that isn't compatible is "Disable Ctrl-Q Shortcut". It's an addon I really don't want to get rid of, there have been many cases in the past where I've accidentally pressed ctrl+q instead of ctrl+w, and had Firefox quit on me.. Edit: The page for the addon has a comment saying it does work with multiprocess, so I just forced it on. I'm on Linux, and I don't know of an about:config key to dis…

If you're on OS X, you can override per-Application shortcuts to achieve the same effect. Not sure about other OSes

Re: Update on Multi-Process Firefox

#85
post #12

Earlier quoted context omitted.

You can figure out what add-ons are compatible by cross-referencing http://www.arewee10syet.com/

Seems the only addon I use that isn't compatible is "Disable Ctrl-Q Shortcut". It's an addon I really don't want to get rid of, there have been many cases in the past where I've accidentally pressed ctrl+q instead of ctrl+w, and had Firefox quit on me.. Edit: The page for the addon has a comment saying it does work with multiprocess, so I just forced it on. I'm on Linux, and I don't know of an about:config key to dis…

I think you can set that in `about:config` without a plugin

Re: Update on Multi-Process Firefox

#86
post #62
post #7

Earlier quoted context omitted.

Isn't this exactly what the article explains and clarifies?

Yes but why bother actually reading the article when you can shoot off in the comments with minimal effort? If you're wrong, someone will correct you. Amirite?

or just post a snarky reply that adds completely NULL to the discussion...

Re: Update on Multi-Process Firefox

#87
post #18

Earlier quoted context omitted.

> You can see on the Add-ons Manager page if a particular add-on is compatible. You can? Where? (Of course, it may be a version thing.)

You need an add-on for that: https://addons.mozilla.org/en-US/firefox/addon/add-on-compat... That's not enough though. In about:addons all my add-ons are listed as compatible, but about:support still says that multiprocess is "disabled by add-ons". So YMMV. EDIT: The gotcha is that the current release uses a whitelist of only about 20 extensions. If you have anything else, you need to force-enable the feature, even i…

Firefox: Trouble managing your addons? Here, have this other addon!

Re: Update on Multi-Process Firefox

#89

Looks like accessibility tools (e.g. screen readers) also disable multi-process support as of Firefox 50. I know enough about accessibility APIs and their implementations to guess that it's going to be difficult to modify that code to work efficiently in a multi-process configuration.` Edit: I'm talking about Windows. Don't know about other platforms.

I'm the dev who is responsible for the Windows implementation. It has been quite the... gnarly experience to say the least. We were shooting for 52 for enabling a11y+e10s, but it is increasingly looking like we're going to need to slip to 53.

Re: Update on Multi-Process Firefox

#90
post #18

Earlier quoted context omitted.

> You can see on the Add-ons Manager page if a particular add-on is compatible. You can? Where? (Of course, it may be a version thing.)

You need an add-on for that: https://addons.mozilla.org/en-US/firefox/addon/add-on-compat... That's not enough though. In about:addons all my add-ons are listed as compatible, but about:support still says that multiprocess is "disabled by add-ons". So YMMV. EDIT: The gotcha is that the current release uses a whitelist of only about 20 extensions. If you have anything else, you need to force-enable the feature, even i…

How great would it be if that add-on were incompatible with multiprocess?
Post reply on HN