Please enable e10s (multi-core CPU processing) support

[est31]

Would it be possible to determine whether this add-on is compatible with the e10s "electrolysis" feature of Firefox[1]?

If it is, the manifest should say so: [2]

This link may help when determining support: [3]

Compatibility of this addon with e10s is required to enable the e10s feature, which brings many speedups and enhancements, on default configured ubuntu installations.

Thank you!

[1]: https://wiki.mozilla.org/Electrolysis
[2]: https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#multiprocessCompatible
[3]: https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox

[Nizar Kerkeni (nizarus)]

Actually the plugin is not compatible with multiprocess.

[drwt (6lobe)]

Considering the next version of Firefox (50) to be released 2016-11-08 will have e10s enabled for all compatible extensions, it would be good to have this addon compatible by then or all Ubuntu users will be left out.

See: https://wiki.mozilla.org/Electrolysis#Add-ons_Schedule

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[drwt (6lobe)]

Well, Firefox 50 got released but Ubuntu users cannot benefit from e10s because this is not fixed.

The next Firefox release will enable e10s for all addons, if ubufox is still broken by that time all Ubuntu users will have a broken default browser.

[Shu Hung (Koala) (koalay)]

I am using Firefox 49 and confirm to have this issue. The page "about:support" shows "Multiprocess Windows" as "0/1 (Disabled by add-ons)".

This issue cause problem with Firefox touch support (see my ticket here: https://bugzilla.mozilla.org/show_bug.cgi?id=1213342). Please take care of the issue. Thanks.

I'm using Ubuntu 16.10, ubufox 3.2 with Firefox 49.

[Cavia Porcellus (caviaporcellus)]

I think the Ubuntu modifications just need to be marked as multiprocess compatible, since I've been forcing Firefox to use e10s (extensions.e10sBlockedByAddons set to false) for over a month and have had noticeable bugs or issues.

[Rocko (rockorequin)]

extensions.e10sBlockedByAddons = false is working fine for me as well.

[Jatan (uncertainquark)]

Any update on this?

Firefox is already on v52 and on its way to have more than 2 processes as default soon. Also, Firefox 57 will remove legacy add-ons support altogether and go web extensions only.

Please update the ubufox add-on to a web extension soon.

[Jatan (uncertainquark)]

Ubuntu users are not benefiting from the vastly improved performance sure to e10s, while other Linux distributions are.

[Rocko (rockorequin)]

FWIW, my firefox frequently freezes (it randomly stops refreshing its window for a few seconds), but with the two unity plugins disabled, the freezes are far less noticeable because scrolling still works.

[Shih-Yuan Lee (fourdollars)]

ubufox is not a necessary ext for firefox.
You should be able to remove it by `sudo apt-get purge xul-ext-ubufox".

[Jatan (uncertainquark)]

The bug is not "Invalid". We know its not a necessary extension, but that
was not the point. The point is it chimes by default and is ON by default,
because of which Firefox runs without e10s multiprocess. This makes all
default Ubuntu users run Firefox at lower performance than it can. I
suggest you keep the bug open and have it fixed in a proper way, which is
to either make the add-on a wen extension which is compatible with all
future Firefox releases.

On 28-Apr-2017 7:31 AM, "Shih-Yuan Lee" <email address hidden> wrote:

ubufox is not a necessary ext for firefox.
You should be able to remove it by `sudo apt-get purge xul-ext-ubufox".

--
You received this bug notification because you are subscribed to a
duplicate bug report (1658407).
https://bugs.launchpad.net/bugs/1627808

Title:
  Please enable e10s (multi-core CPU processing) support

Status in Ubufox Extension:
  Confirmed
Status in firefox package in Ubuntu:
  Invalid
Status in ubufox package in Ubuntu:
  Confirmed

Bug description:
  Would it be possible to determine whether this add-on is compatible
  with the e10s "electrolysis" feature of Firefox[1]?

  If it is, the manifest should say so: [2]

  This link may help when determining support: [3]

  Compatibility of this addon with e10s is required to enable the e10s
  feature, which brings many speedups and enhancements, on default
  configured ubuntu installations.

  Thank you!

  [1]: https://wiki.mozilla.org/Electrolysis
  [2]: https://developer.mozilla.org/en-US/Add-ons/Install_Manifests#
multiprocessCompatible
  [3]: https://developer.mozilla.org/en-US/Add-ons/Working_with_
multiprocess_Firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubufox/+bug/1627808/+subscriptions

[Shih-Yuan Lee (fourdollars)]

Just invalid for Firefox.
This issue is still valid for ubufox.

[Jatan (uncertainquark)]

Its important to not that this bug is also affecting all distributions using Ubuntu repos, like elementary OS for example. It is affecting performance on Ubuntu as well as other distros.

[Shih-Yuan Lee (fourdollars)]

Hi, I just made an unsigned ubufox xpi to fix the problem.
Would you like to follow https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox to manually install this xpi to see if there is any regression?

[Christian Assig (chrassig)]

Shih-Yuan Lee, before I saw your comment #15 here, I uploaded a change in Launchpad, containing exactly the same line in the same file (install.rdf), even at the same position:

<em:multiprocessCompatible>true</em:multiprocessCompatible>

https://code.launchpad.net/~chrassig/ubufox/multiprocessCompatible/+merge/325042

[Ian (imyxhuang)]

Looks like there's been no activity by the developers on ubufox since September 18th, 2015, and the last accepted merge was on 2012...
I think I'm going to be disabling this for a few years until either of the above merges are accepted.

[drwt (6lobe)]

Due to this bug Ubuntu users cannot benefit from web content sandboxing.

[est31 (mtest31)]

Just wanting to point out that in nightly firefox, the switch to disable legacy add ons (which this add on is) has been flipped.

[Jeremy LaCroix (j-jlacroix)]

@est31, that's great news. That means if Canonical doesn't disable this addon by default, Mozilla will.

Should I submit a patch somewhere to remove this addon as a dependency? It seems to me that there's no value here, all it really does at this point is slow down the browser. I don't see any logical reason to include an addon by default that will only make people's experiences worse.

[drwt (6lobe)]

This isnt just a performance issue, this is a security issue.

Due to this addon Firefox on Ubuntu cannot utilize web content sandboxing (which obviously depends on e10s) which means Ubuntu users are being left vulnerable to security issues.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubufox - 3.3-0ubuntu2

---------------
ubufox (3.3-0ubuntu2) artful; urgency=medium

  * Add Build-Depends on zip
    - update debian/control

ubufox (3.3-0ubuntu1) artful; urgency=medium

  * New upstream release
    - Add multiProcessCompatible to the install.rdf. Thanks to Shih-Yuan Lee
      for this (LP: #1627808)
    - Drop the signed extension from the source tree - this isn't needed for
      system addons anymore

  * Update packaging to build the addon xpi again
    - update debian/rules

 -- Chris Coulson <email address hidden> Mon, 14 Aug 2017 13:09:08 +0100

[drwt (6lobe)]

Are we going to see this fixed also in other supported versions like 16.04?

[Shih-Yuan Lee (fourdollars)]

https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa has included 14.04, 16.04 and 17.04.
I guess they will be released soon.

[drwt (6lobe)]

Thank you, that is great to hear!

[est31 (mtest31)]

Thanks for resolving!

The fix won't last though, as Firefox 57 onward will only load web extensions. I've filed bug #1711778 as followup to track porting of this add on.