"How much crashed?" - I didn't spot this selection when submitting originally. Actually the whole browser crashes.

Tested this issue on Android and no crash is seen when adding https://llama.vision or  https://snapw.at to home screen.

Chrome versions tested:
70.0.3538.80

OS:
Android 9.0

Android Devices:
Pixel 2 XL

@peter: Could you please confirm details of device you are seeing this issue.Also let us know if this crash is consistent?

From the crash id mentioned in c#0,stack trace looks similiar to Issue 892627. Hence, cc'ng @ryansturm from Issue 892627 for further inputs on this.

Thanks!

It's a Pixel 2 (non-XL). Still seeing the same result today. Yes, a consistent crash for me - happens every time I tap that small Add to homescreen banner at the bottom. (Just checked another site, it also happens at https://pwa.rocks).

Thank you for providing more feedback. Adding the requester to the cc list.

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

Not a lot for me to go on with the single line stack. I only see 3 crashes total in M70 for RemoveInfoBarInternal, so I'm not sure what's going on. There are crashes in M71 for capping pages that has already been fixed, but this largely looks unrelated based on the video.

Adding pkasting@ to cc to see if he has any insight here.

Just let me know if I uploading another crash report would help, or if I
can provide a better stacktrace somehow. (I tried to upload another report
today, but I wasn't on wifi and it seemed to be stuck queueing. But I can
try again from home!)

On Fri, 2 Nov 2018, 18:37 ryanst… via monorail <
monorail+v2.2572660371@chromium.org wrote:

As per comment#4 re-tested the issue on Pixel 2 with steps mentioned in comment#0, Page added to homescreen successfully without any crash. Attaching screencast for reference. Please check it and let us know if we miss anything. Another crash id would help in further triaging.

Thanks!

Deleted: 20181105_170446.mp4 8.2 MB

	20181105_170446.mp4 8.2 MB View Download

Here's a screencast from mine. Also a screenshot of the 'crashes' page - I've just uploaded crash ID b8cffc28646135f8 which should correspond to the one from the screencast.

Deleted: 2018_11_05_11_56_05.mp4 14.2 MB

	2018_11_05_11_56_05.mp4 14.2 MB View Download

Deleted: Screenshot_20181105-115818.png 298 KB

	Screenshot_20181105-115818.png 298 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

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

Weirdly, I can see this reproing for a user consistently but only for that one user. There's nothing obviously screwy in the reports. The crash itself seems like potentially a dangling pointer but the stack is getting corrupted.

Perhaps it's possible you tweaked some about:flags for PWAs that's entering a corrupt state or conflicting with an experiment? You could tyr clearing app data? I'm also curious if other chrome channels repro - could obvoiusly be something in chrome code or could just be a config issue or something about the device. Pretty strange tbh

As per comment#11 adding Needs-Feedback label.

@ peter: Could you please check the issue on various chrome channels as per c#11 by resetting all flags to reset.

Thanks!