On 17/04/2016 22:54, Mike Conley wrote:
Generally speaking, Firefox's stability has not been good for me for 2-3
months. I'd like to file a bug, > but I've already used up my quota of
unactionable bugs, and if I dug into all of my idiosyncratic
issues I'd never get any work done. I seem to do things differently, in
some problematic way. I wish I > could get more use out of the profiler &
cleopatra, but when I'm having issues it often can't manage
to load that page successfully. Plus, for some reason I am mentally
incapable of getting useful
(actionable) data out of that UI (or the necessary data isn't there? not
sure.) PEBKAC, I'm sure.
(Sorry for the dupe, sfink, since the first version only went to you)
This kind of sentiment concerns me a bit. Oftentimes, people will report
odd or undesirable behaviour from Firefox and we have to do painstaking
(and sometimes lossy) diagnosis over Bugzilla. When it's somebody within
the organization, I really don't think there's an excuse for us not finding
some kind of explanation for what's going in a situation like this - like,
we have (sorta[1]) access to the machine. I feel like that should be a
golden opportunity.
If we can't keep people in the org satisfied with the performance and
stability of Firefox, then I think that's a problem.
I'll bite on a somewhat related issue to sfink's original point:
reasonably often, perf bugs get filed that reach a stalling point
sometime after we have a cleopatra profile and before we know what's
going on. Sometimes I can't reproduce (
https://bugzilla.mozilla.org/show_bug.cgi?id=1205110 ) and sometimes I
can ( https://bugzilla.mozilla.org/show_bug.cgi?id=1225900 ).
Unfortunately, usually (not always) I'm in the same place as sfink in
that I struggle to find something specific in the profiler to point at
and use to triage the bug, irrespective of whether the profile is mine
or provided by someone else. Some folks on the QA team ping me about
bugs every now and then, I take a look, and if I get stuck, too, I'm not
really sure where to go with them.
So the more general question I have here is: what to do with bugs that
get "stuck" like this? Obviously it doesn't scale to just point mconley
to all these bugs (awesome though he may be), or to do the same with
:overholt (though I notice that the second bug has since gotten at least
slightly more traction through his efforts - thanks!). Web perf bugs
don't seem to have a clear home before we triage what, specifically, is
causing the issue, which is often difficult on production sites with
minified JS, A/B testing, region-specific ads etc.. Am I just missing
something? Is there someone / a team / a flag that takes point on stuff
like this?
~ Gijs
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
