From 853301 bug comment 32:
"Similar to the previous landing, this regressed Ts by ~25ms, tpaint by about 10ms, and increased various memory counters. Possible clue: "Tp5 No Network Row Major MozAfterPaint (Main Startup File IO Bytes)" regressed by 34% (about 10MB).
If this patch stays in, we'll need follow-up bugs to fix the regressions. They should be nominated for tracking-firefox25."
Naveed, how do you plan to address this? Should we worry about this in the FF25 timeframe? If so, do we have alternatives such as disabling part of bug 853301?
(In reply to Alex Keybl [:akeybl] from comment #1)
> Naveed, how do you plan to address this? Should we worry about this in the
> FF25 timeframe? If so, do we have alternatives such as disabling part of bug
This will pretty much be fixed once bug 919872 lands.
Also, if I'm not mistaken, the original regression was backed out before branch uplift, so technically there's nothing in any tree to unregress. Only once Intl is enabled in desktop builds could there possibly be any regression -- but with bug 919872 landed, I'm fairly sure there'll be no regression any more.
The landing management in bug 853301 has not been great. As I understand it, bug 853301 comment 41 was a trunk disabling, and bug 853301 comment 64 re-enabled building of it, but doesn't expose it (so still no Talos impact). So 25 up to trunk are not "affected", and we don't need to track this for 25.
[Mass change filter: core-js-intl-api-move]
I don't think this is relevant anymore.