(In reply to Boris Zbarsky [:bzbarsky, bz on IRC] from comment #15) > Oh, and the fix I pushed definitely resolved the responsiveness issue in my try pushes. Are you saying it didn't resolve it on the non-try trees? Yes, that's what I'm thinking. According to [this graph](https://treeherder.mozilla.org/perf.html#/graphs?series=autoland,1648915,1,1&highlightedRevisions=e657fe2ca2a3&highlightAlerts=0), the push didn't cause any perf win on responsiveness. Now, there are some possible explanations: either bug 1351078 is related to the fix from comment 10 and resolved it first **or** there's something fishy going on with the PGO build that's not catching the fix immediately **or** another regression landed near our fix and confused me.
Bug 1528762 Comment 16 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Boris Zbarsky [:bzbarsky, bz on IRC] from comment #15) > Oh, and the fix I pushed definitely resolved the responsiveness issue in my try pushes. Are you saying it didn't resolve it on the non-try trees? Yes, that's what I'm thinking. According to [this graph](https://treeherder.mozilla.org/perf.html#/graphs?series=autoland,1648915,1,1&highlightedRevisions=e657fe2ca2a3&highlightAlerts=0) which highlights bug 1528762's landing, the push didn't cause any perf win on responsiveness. Now, there are some possible explanations: either bug 1351078 is related to the fix from comment 10 and resolved it first **or** there's something fishy going on with the PGO build that's not catching the fix immediately **or** another regression landed near our fix and confused me.