1083545 - [e10s] Add AMO compatibility overrides for add-ons that break Firefox when e10s is enabled (before e10s rides the trains)

Status: RESOLVED WORKSFORME

(Firefox :: Extension Compatibility, defect)

Description

[Chris Peterson [:cpeterson]]

We should blocklist addons that cause serious Firefox problems when e10s is enabled, like hangs or crashes.

For example, bug 1027967: the "Cloud To Butt" addon hangs Firefox for 10 seconds on every page load.

Comment 1

[Achwaq Khalid]

Great! The fastestFox addon Bug 1037200 will slow down the starting time by a factor of X10

Comment 2

[Jorge Villalobos [:jorgev] (he/him)]

The blocklist is not appropriate for this. We have compatibility overrides which make more sense. We can flag add-on version ranges with Firefox version ranges and they will appear as incompatible to users.

Comment 3

[Chris Peterson [:cpeterson]]

Thanks, Jorge. I updated the bug summary with your recommendation.

Comment 4

[Kent James (:rkent)]

I believe this will be affected by bug 1183733 if compatibility overrides are used instead of blocklists.

Comment 5

[Chris Peterson [:cpeterson]]

We still care about this bug. Even though we plan to make add-ons opt into being e10s-compatible (MPC), some could still cause e10s problems.

Comment 6

[:shell escalante]

moving under deployment bug... this is relevant for stage 3 or 4 (after the enabling - eventually comes how we handle disabling decisions.)  In PM's sights now - based on metrics and as much analysis as we can get before hand.

Comment 7

[:shell escalante]

closing as with 57 we have only add-ons that are webextensions.  For issue with earlier versions we use standard blocklisting or a max version (usually max version - to go pre-e10s).