Yang, any clue if this a problem with Chrome or Android?

Being intermittent and on Android... might be a bug in the optimizing compiler on ARM? 

Here is a list of device I was able to reproduce the problem:
- Nexus 7, Android 6.0.1 Chrome/59
- Galaxy S7 (SM-G930W8 unlocked) Android 6.0.1, Chrome/59
- Galaxy S7 (SM-G930W8) Android 7.0, Chrome/59

I was never able to reproduce on MacOS/X, Linux (x86_64), Windows. So it looks more like an Arm optimzer based problem. 

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

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

Is this still a problem?

Hi,

Sorry for the delay, I have no way to re-test the problem. I think I
remember a fix being posted in the low-level optimzer in V8. But I didn't
keep track because the fix I proposed was included in the sjcl library and
so the workaround works for me.

If you need more involvement from me, let me know.

I guess you can close this bug. Thanks for the follow up.

Have a nice day,

Sébastien