On 2014-03-20 5:38 PM, Gavin Sharp wrote:
On Thu, Mar 20, 2014 at 10:38 AM, Irving Reid <irv...@mozilla.com> wrote:
For unknown reasons, internal bookkeeping prefs used by AddonManager and
XPIProvider are set to values of the wrong type on some Firefox profiles,
and are now stuck that way. I can write wrapper code on these calls to catch
the error and clear the broken preference, but I wonder if it would be
better to change set*Pref() to force the preference to the intended type.
Which prefs, out of curiosity?
extensions.blocklist.pingCountVersion (146 times out of ~1.5 million
Nightly telemetry sessions) and extensions.shownSelectionUI (8 times in
1.5m)
I could imagine some forms of malware installers clobbering prefs.js
values (or even firefox.js/all.js values, if they have appdir write
access) incorrectly. If that's what's happening here it should inform
our ways of mitigating it. Any way to get more data from the affected
installations?
The prefs in question aren't likely targets for malware, though they
could be collateral damage. They don't have default values in all.js.
We could pull out the full telemetry details for sessions that see these
failures and look for other signals, or we could add more telemetry
probes. I'm not sure the problem is big enough to make those worthwhile.
The exception reporting that I added in bug 952543, which revealed this
issue, just rolled into Beta 29. I'll check the Beta telemetry data next
week to see if it's any different from Nightly.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
