Closed Bug 1245192 Opened 7 years ago Closed 7 years ago

[e10s] Need to block Skype Click to Call users from participating in Beta 45 Telemetry Experiment


(Firefox :: Extension Compatibility, defect)

Not set



Tracking Status
e10s m8+ ---


(Reporter: elan, Assigned: Felipe)




(1 file)

Based on KaiRo's Findings: 
Bug 1210099 (mozilla::OriginAttributes::CreateSuffix) is 7.5% of all crashes in 45.0b1, almost all at startup, 5 crashes per installation, #1 Top Crash Score by far. All seem to have e10s on and most have Skype Click-to-Call installed.

To be fair, this is a pre-release channel so we also need to contact Skype about the crash
Assignee: nobody → felipc
tracking-e10s: --- → ?
So to do this I need the add-on id of the add-on mentioned, and possibly the version range unless we want all versions included.

Note that what we will do is to remove Skype Click-To-Call users from the experiment and return them to non-e10s.
Summary: [e10s] Need to block Skype Click to Call for Beta 45 Telemetry Experiment Participants → [e10s] Need to block Skype Click to Call users from participating in Beta 45 Telemetry Experiment
From KaiRo: 
82AF8DCA-6DE9-405D-BD5E-43525BDAD38A} is the ID, see and are crashing, and I think the latter is actually their newest version, from looking at the data we have

Thanks! Since both an older and the newer version are crashing, I'm inclined to block all version from the experiment.

From that comment, do we also want to block the avast add-on? Or wait and see?
Attached patch patchSplinter Review
I have verified locally that a change in the filter.js file to return false does trigger an uninstall in the experiment system, and that our add-on code is correctly clearing the e10s pref when uninstalled.
Attachment #8714951 - Flags: review?(wmccloskey)
Note that we're in contact with Skype/Microsoft in bug 1215970. I'll let them know about this new crash.
Comment on attachment 8714951 [details] [diff] [review]

Review of attachment 8714951 [details] [diff] [review]:

I guess if this helps we should do it. I doubt this add-on is actually responsible for the crash though.
Attachment #8714951 - Flags: review?(wmccloskey) → review+
Depends on: 1245300
Block deployed. Users with this add-on id should be taken out of the experiment, as long as the crash doesn't happen too early in the startup that they can't get the updated manifest.
You need to log in before you can comment on or make changes to this bug.