This is also occurring on M62 9901.66.0 Stable

Render Crashes with no symbols
https://crash.corp.google.com/browse?stbtiq=4a4969256b302545&sql_dialect=googlesql#0
https://crash.corp.google.com/browse?stbtiq=bdbaa0c5057a880a&sql_dialect=googlesql#0

was this happening on previous stable 9901.54.0	62.0.3202.74?

Mike, are you aware of any recent change on symbols uploading?

Yes, Symbols are missing for previous stable build  9901.54.0	62.0.3202.74

Crash links:
https://crash.corp.google.com/browse?stbtiq=671bee43085b1618&sql_dialect=googlesql
https://crash.corp.google.com/browse?stbtiq=e3e8a9f3dc7c3c1b&sql_dialect=googlesql

Crash info from server:
https://crash.corp.google.com/browse?q=product.Version%3D%2762.0.3202.74%27%20AND%20product.name%3D%27Chrome_ChromeOS%27%20AND%20custom_data.ChromeCrashProto.channel%3D%27%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27&sql_dialect=googlesql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#-property-selector,+samplereports

 Symbols missing in M63 e.g. edgar.

https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_ChromeOS%27%20AND%20product.version%3D%2763.0.3239.26%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27start_thread%27&sql_dialect=dremelsql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=39a5e736da0ae7a0&index=0#5

+dgarret too 

i don't think it's related to symbol upload.  there are crashes from the same build & board & release where symbols are missing and symbols are found:

63.0.3239.26 on monroe-signed-mp-v2keys
https://crash.corp.google.com/browse?stbtiq=7d7b9dac2ef026e4  missing
https://crash.corp.google.com/browse?stbtiq=9868427dca135cf7  found

if you look at the builds where symbols are missing, the chrome debug id is wrong:
https://crash.corp.google.com/browse?stbtiq=7d7b9dac2ef026e4#5
0x00007fe075e00000	0x00007fe07c181000	/opt/google/chrome/chrome		000000000000000000000000000000000

the debug id is given to us by Chrome itself as part of its minidump creation.  crash-reporter just passes along the dump it was given.  so someone on the Chrome side needs to own this.

+ivanpe@, +thakis

Ivan/Nico, are you aware of recent changes/known issue with debug id for crash reporting?

If you look at the "Modules" tab for the reports that is missing symbols (https://crash.corp.google.com/browse?stbtiq=7d7b9dac2ef026e4#5_, you'll see that the Debug Identifier is: "000000000000000000000000000000000".  This is known issue in Breakpad client.

For more details: https://groups.google.com/a/google.com/d/msg/crash-team/v9LrkzzNySs/AJt4tOzRAgAJ

We expect this to be fixed in Crashpad.  The Crashpad client for Android and Linux is almost ready.  The Crashpad client for ChromeOS is expected in Q1-Q2 2018.

Resolving as "won't fix" as we are actively working on the Crashpad clients and we don't plan to fix this in the Breakpad client.

 Issue 791868  has been merged into this issue.