Crashing like a hell on OOS 11.1.10.10.AC01DA

[NoName42]

[Saoiray]

@NoName42 Not sure how @sampson has his notifications set here, but a little advice from me is to always tag a person when you respond. Just simply replying on a topic is not likely to send notifications to a person. I’ve had a lot of people lost because they did a simple reply and I never knew it.

So I’m seeing your Crash Report ID as:

• cfa0700-4b76-f809-0000-000000000000

• ccaf0700-4b76-f809-0000-000000000000

• caaf0700-4b76-f809-0000-000000000000

• c7af0700-4b76-f809-0000-000000000000

• c5af0700-4b76-f809-0000-000000000000

• c3af0700-4b76-f809-0000-000000000000

• c1af0700-4b76-f809-0000-000000000000

• bdad0700-4b76-f809-0000-000000000000

• bbaf0700-4b76-f809-0000-000000000000

• b7af0700-4b76-f809-0000-000000000000

[NoName42]

Thanks for the response!

[Saoiray]

Actually, let me tag @Mattches too as I know he can pass on crash logs to team. Also if Sampson might be busy with other things or not getting notifications, can tag him in if necessary.

[Mattches]

Passing these IDs along to the team, thanks all.

[Mattches]

It appears that this may be related to a known issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=1280378

@NoName42 can you please try disabling autofill on your Android device to test and see if the browser still crashes?

Thank you

[NoName42]

I disabled autofill, and browser seems to work fine.

But is there not any more convenient solution rather than disabling autofill?

Thanks for the help

[Mattches]

At this time no, that is the only solution. It is good to know that the crash is due to this known issue. I believe that we are working with the Chromium team to resolve this issue. Apologies for the inconvenience in the meantime.