4 ms·
Until it gets activated again with the next restart or update.
by _Codemonkeyism 9y ago
Until it gets activated again with the next restart or update.
- sfink 9y agoPlease, if anyone has steps to reproduce this behavior (beyond anecdotes of other people experiencing it), please file a bug. We engineers (I work on spidermonkey) put a lot of effort into making sure opt-in things are truly opt-in, and make sacrifices as well. (I would love to be able to automatically gather cpu or memory profiles with full urls included, to make it easier to reproduce field problems. Heck, we can't even tell if a set of crash reports comes from the same user. But I'd rather not have any of that, given the privacy risks. )
- lucideer 9y agoThe Mr. Robot thing is not the first one of these issues we've seen with Firefox, but most of them (from my anecdotal perspective) seem to be either with web dev (teams managing moz web properties), ui design (e.g. the privacy issues in about:addons I linked to in a comment above) or extensions development* (this Mr. Robot thing, Pocket, and a lot of issues with the entire Test Pilot project). I'm curious about whether the problems being discussed in the article above are not so much systemic to Mozilla itself (as many commenting here fear), but rather an issue with management of certain teams within the organisation. * I refer here to teams working on web extensions, rather than those working on web extensions APIs.