Users experienced this crash on the following builds:

Android Dev 63.0.3219.0 -  0.34 CPM, 3 reports, 3 clients (signature mmap)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Android Beta 62.0.3202.29 -  0.25 CPM, 36 reports, 21 clients (signature mmap)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Just to update the latest behavior of the crash:

Still seeing crash instances on latest Dev-63.0.3223.7 & stable-61.0.3163.98.

63.0.3223.7	1.45%	11	-Dev (from 9 clients)
61.0.3163.98	1.05%	8	-Stable (from 6 clients)

Link to the list of builds:
--------------------------
https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Android%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27gpu-process%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27mmap%27&sql_dialect=dremelsql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#-property-selector,productversion:1000

Thanks..!

Missing system symbols for Linux/Android.

I already explained this is crbug/766752.

Unfortunately, issues with stack trace quality on Android/Linux are pretty common and there is not much we can do at this point. The reason is that there is no universal public symbol server for device manufacturers to upload their symbol files (in this case symbols for libc.so and others), so there is no good source for symbol files we can use.

Things are better on other platforms.  Microsoft provides public symbols server containing symbols for all versions of Windows.  For Mac OSX and iOS, we can manually extract the symbols from devices running the OSes.

For Android/Android, we have though about extracting symbol files directly from the client devices (via our Breakpad/Crashpad clients) but these efforts are still in ideation phase.