It hasn't been secure for 18 months it happens everyday, so aim not able to produce a working version. 

Do you have reproduction steps for this crash?

The crash is happening in GoogleMobile App, which has just recently switched to Cronet framework.

Crashing thread doesn't have Cronet on it:

Thread 0 name:  Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   libsystem_kernel.dylib        	0x0000000184423224 0x184422000 + 4644
1   libsystem_kernel.dylib        	0x000000018442309c 0x184422000 + 4252
2   CoreFoundation                	0x00000001853f4e88 0x18531a000 + 896648
3   CoreFoundation                	0x00000001853f2adc 0x18531a000 + 887516
4   CoreFoundation                	0x0000000185322d94 0x18531a000 + 36244
5   GraphicsServices              	0x0000000186d8c074 0x186d80000 + 49268
6   UIKit                         	0x000000018b5d4130 0x18b55f000 + 479536
7   Google                        	0x00000001000c2fe0 0x10009c000 + 159712
8   libdyld.dylib                 	0x000000018433159c 0x18432d000 + 17820

yesterday's crash report

Deleted: Text File 2.txt 64.1 KB

Text File 2.txt 64.1 KB View Download

Thank you for providing more feedback. Adding requester "olivierrobin@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

this may help, seems it's the route cause as usual

this may help 

yesterday's and today's.

Deleted: Text File 3.txt 74.3 KB

Text File 3.txt 74.3 KB View Download

Deleted: Text File 5.txt 64.1 KB

Text File 5.txt 64.1 KB View Download

Removing network library - looks like a WebKit crash.

No offence intended but you could remove everything and it won't work. I've spent thousands on new devices over the last 18 months, all ending up with the same crashes. I've just recently come across a new undifined bug in iOS but not chrome,goole related so haven't posted  there's something we are missing probs to do with memories more related to a user than a device.

Also just to clarifymultiple networks have also been used 

Do you have reproduction steps?
Particular queries or URL you browse?

So I'll take you  u back to latest software update.
Then ikgo back as far as I can , spot the difference ipf you can 

This is not a bug in Chrome for iOS product (at least according to crashlogs). jonwall@ or kevinis@ this looks like iGSA crash, so could you please file it as iGSA internal bug. Thanks!