Closed Bug 1128121 Opened 10 years ago Closed 7 years ago

[e10s] Collect telemetry for the multiprocessCompatible flag

Categories

(Toolkit :: Add-ons Manager, defect, P3)

defect
Points:
1

Tracking

()

RESOLVED DUPLICATE of bug 1358620
Tracking Status
e10s + ---

People

(Reporter: mossop, Assigned: gkrizsanits)

Details

Split off from bug 1040158. Chris I'm, unsure exactly what we want here, do you just want to add the multiprocessCompatible flag to the existing add-on data in telemetry or is there something else?
Flags: qe-verify-
Flags: needinfo?(cpeterson)
Flags: firefox-backlog+
Good question. I *think* that bug was suggesting we collect telemetry on add-ons that claim to be multiprocessCompatible but hit shim code paths. However, that information wouldn't be actionable because we wouldn't know which "compatible" add-ons are hitting which shims. We can probably WONTFIX. Bill should know.
Flags: needinfo?(cpeterson) → needinfo?(wmccloskey)
This isn't actionable until we have decided what we want here and doesn't seem like it should be m5 fodder anyway.
Well, Blair originally asked for this in https://bugzilla.mozilla.org/show_bug.cgi?id=1029926#c11. I suspect he just wanted to find out how many add-ons are marked multiprocess compatible.
Flags: needinfo?(wmccloskey)
Flags: needinfo?(bmcbride)
IIRC, I was just thinking of having that flag added to the existing add-ons details in telemetry.
Flags: needinfo?(bmcbride)
Assignee: nobody → gkrizsanits
We've decided the last time that this should be a plus instead of m8 but I can't set it to + only to re-triage...
Bill, do we still want this?
Flags: needinfo?(wmccloskey)
It might be nice to have, but it's not very important.
Flags: needinfo?(wmccloskey)
Priority: -- → P3
This got added in the referenced bug.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.