This is a renderer process crash on Android.  Issue 646643 is a browser process crash on Windows, so it's not a duplicate.

They shouldn't be merged just because the crash signature is "da39a3ee_5e6b4b0d_3255bfef_95601890_afd80709".  See issue 646960 for why.

Any news on this issue?


I collected further information for investigating this problem.

We tested the above web app on different devices with different Android and Chrome versions. The problem occurs on Nexus 5, Nexus 5x, Nexus 6, Samsung Galaxy Tab S2, Motorola Moto G, HTC One M9 and lots of others, currently all with Chrome 53.0.2785.124, one with 52.0.2743.98.
We could not reproduce the bug with Chrome 51.0.2704.81 or 50.x.

We could exclude some possible error causes:
- web fonts / svg / image loading
- css
- server calls network latency
- animations
- sourcemaps
- app code changes of past 3 months
- third party scripts/css loading

My investigation leads to the assumption that the process crashes during js processing/iterating through deep nested data structures. The erroneous behaviour is non-deterministically. 
Since Chrome does not give a meaningful error message, it is quite difficult to find the cause for the problem. 
The Chrome DevTools give no hint for a memory leak or the like.


Please help in solving the problem.
If you need further information, please contact me.

Thanks.

problem persists, also in the Dev version 56.0.2913.5

I've tried on a Nexus 5 with Chrome 69.0.3441.0 and it no longer reproduces. Closing stale issue.