The user said the issue went away after installing the latest build. Should this be closed now?

#1: the issue is not present in a previous build (3029.82) but the most recent build (3071.27) crashes.

Updated summary.
Is this the only report against M59 (beta)?

User stated "Version 58.3029.82 (58.0.3029.82) works fine, but new build 59.3071.27 (59.0.3071.27) crashes". This concerns me because M58 (app store) is expected to work. M59 is in test flight and crashed.

I don't know what other information we can get from the user. All crash dumps are probably gone since user has deleted the crashing app and downloaded another version.

No crashes seen on clean install of build 60.0.3086.0 Canary on iPhone 7+ and iPad Pro.

sczs: please look and see if go/gusmr is the right crash here.

Its not the exact crash since the user device info doesn't match the one in the crash report. Though it could be a similar crash.

I will keep an eye on this, though I think our refactoring should still be trivial enough to not introduce these crashes.

ccing Yuke: Do you think some of the "request Mobile/Desktop site" changes/refactoring could be related?

Ping Yuke?

Unfortunately, there is enough information for me to make a conclusion. Is there a way we can try to re-pro with the exactly same version?

I fetch the Dev build for 59.0.3071.27 and installed it. New installation. No crash.

I'm marking this as WontFix. If this happens again, we should ask user to provide the output of chrome://crashes