1046053 - "MEGA" add-on does not work with e10s

Status: VERIFIED FIXED

(Firefox :: Extension Compatibility, defect)

Description

[bull500]

Error setting up DOM Storage instance:

[Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIXULAppInfo.vendor]"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame :: chrome://mega/content/secureboot.js?r=11580382 :: <TOP_LEVEL> :: line 68"  data: no]

undefined

Comment 1

[bull500]

This was installed from the offcial mega.co.nz site. The add-on listed on the default mozilla source is old.

Comment 2

[Chris Peterson [:cpeterson]]

bull500, thanks for testing! I'll update our list of add-ons.

Comment 3

[jpjchavez]

Hello... well, I´m an user and I wanna try to solve that mistake in my pc... Could you help me please? Greetings from Peru :D

Comment 4

[Chris Peterson [:cpeterson]]

hi jpjchavez, this looks like a bug in MEGA's add-on. They will probably need to fix their code, unless Ally wants to shim nsIXULAppInfo.

Comment 5

[Chris Peterson [:cpeterson]]

gk, do you know who maintains the MEGA add-on for Firefox?

It is not compatible with multiprocess Firefox (e10s). If you have any questions about add-on support for e10s, just drop by the #e10s IRC channel on irc.mozilla.org. MDN also has a good introduction:

https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox

Comment 6

[gk]

Thanks for letting me know. I'll forward this internally and see what can be done.

Comment 7

[gk]

OK, passed on the info, we're working on fixing it (should be minor as I was told), and the fix should then hopefully be part of our next update (due very soon, hopefully in a few days).

Comment 8

[gk]

One last note: I was told the problem is the still missing appinfo interface, which might otherwise break many addons compatible with both Desktop and Android browsers, too.

Comment 9

[Tomislav Jovanovic :zombie]

(In reply to gk from comment #8)
> One last note: I was told the problem is the still missing appinfo
> interface, which might otherwise break many addons compatible with both
> Desktop and Android browsers, too.

even if this gets resolved otherwise, i filed bug 1061873..

Comment 10

[Chris Peterson [:cpeterson]]

Thanks, gk. That was fast! :) We will investigate the appinfo issues you reported.

Comment 11

[gk]

Sweet, thanks.

/me is quite stoked that our add-on is already being tested against e10s.

Comment 12

[gk]

From our Firefox extension developer: He has declared the problem to be resolved in our code base, but that might be subject to change, as it's been tested on Firefox 35.0a1 20140904030202 WINNT x86-msvc. The app has been updated on our site today, so it might be worth re-testing for your case with e10s.

Comment 13

[Chris Peterson [:cpeterson]]

Thanks, gk!

bull500: when you have time, can you please test the new version of MEGA's extension with e10s? Thanks!

Comment 14

[bull500]

ah sorry, but on Fedora Linux 20, its still kinda broken :(

Pop-up box after installing the new add-on from the site:

Unable to initialize core functionality:

[Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIPrefBranch.setBoolPref]"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame :: chrome://mega/content/fileapi.js :: __mozPreferences :: line 907"  data: no]

Firefox 35.0a1 20140907030206 Linux x86_64-gcc3

Comment 15

[gk]

This is feedback I have received from our developer on the above comment by @bull500:

"""
He is not using the latest version. The newest version with a `setBoolPref()` call on line 907 of `fileapi.js` is 2.0.176

I did however check the site and it's indeed providing the correct 2.0.188 version.
"""

Comment 16

[bull500]

(In reply to gk from comment #15)
> This is feedback I have received from our developer on the above comment by
> @bull500:
> 
> """
> He is not using the latest version. The newest version with a
> `setBoolPref()` call on line 907 of `fileapi.js` is 2.0.176
> 
> I did however check the site and it's indeed providing the correct 2.0.188
> version.
> """

everything seems fine with 2.0.188! :)

Last time i downloaded and tested the add-on right after the comment was posted. Maybe the new version wasn't up yet then.

Kudos to the add-on team! :) Works great so far :)

Comment 17

[Chris Peterson [:cpeterson]]

I am closing this bug as FIXED, as per bull500's comment 16.

Comment 18

[Juan Simón]

This isn't solved: http://storage9.static.itmages.com/i/16/1123/h_1479908325_6436899_008335d85b.jpeg

Firefox 50
MEGA addon 3.6.16

Comment 19

[mirh]

(In reply to Simón from comment #18)
> MEGA addon 3.6.16

3.8.6 is reported compatible. 
And if any, that would be more qualified to be discussed under bug 1189385 fiy.

Comment 20

[namanspace]

Running v52.0.1 firefox on Ubuntu 16.04. Mega v3.8.6 is reported compatible, but it isn't.