Traced to this CL


I attempted a fix and messed it up - I think without some more context on what this change was trying 

Traced to this CL 
https://chromium-review.googlesource.com/#/c/436407/

Hi Richard

Any guidance on how to move forward here. Keith tried to fix the issue, but there were other problems. #3 contains the CL that probably is causing this issue. This bug is a release blocker for moblab

Oy.  I can't explain why the revert didn't work for you.

However, if the bug really is what we think it is, there are
fixes we can apply.

The most obvious thing to try would be to cherry pick this CL:
    https://chromium-review.googlesource.com/#/c/450870/

Oy.  I can't explain why the revert didn't work for you.

However, if the bug really is what we think it is, there are
fixes we can apply.

The most obvious thing to try would be to cherry pick this CL:
    https://chromium-review.googlesource.com/#/c/450870/

> Oy.  I can't explain why the revert didn't work for you.

Looking at the git history, there are things I can't explain.

We should probably get a root-cause on exactly what's in the
history, and why.

Meantime, I believe that cherry-picking the cited CL will fix
the problem.

Probably best to let haddowk@ drive the cherry-pick.

This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone.

All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

[Auto-generated comment by a script] We noticed that this issue is targeted for M-58; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-58 label, otherwise remove Merge-TBD label. Thanks.