[Autocomplete] Docs demo crashing on Chrome in an Android phone

[robertkstarr]

Steps to reproduce

Link to live example: (required)

Steps:

1. Visit https://mui.com/material-ui/react-autocomplete/ or https://mui.com/base-ui/react-autocomplete/ using Chrome on an Android Phone (might be specific to Pixel 8 Pro, not sure)
2. In the first dropdown menu, select "The Shawshank Redemption"
3. Then, on the same menu, select "The Godfather"

Current behavior

Chrome returns an Aw, Snap! error page

Expected behavior

Nothing should happen

Context

No response

Your environment

Chrome version 121.0.6167.101 Android 14; Pixel 8 Pro Build/UQ1A.240105.004

Search keywords: autocomplete, chrome, android

[raichshlv]

Crashes on my S22 Ultra as well. Does not crash on Firefox or Brave, but does on Chrome. Also crashes when using Autocomplete in my webapp.

[strouhaljan]

I am experiencing the same in our application using MUI, "@mui/material": "^5.14.14". Galaxy S22, Chrome.

[DiegoAndai]

Hey @rstarr-indeed, thanks for the report.

I can't repro on BrowserStack, Chrome v120.0

https://github.com/mui/material-ui/assets/16889233/129d2da9-7f5e-490e-94be-0510a6c30925

May I ask you to attach a recording of the crash?

@mui/core, does anyone have a physical Android phone they can test this with?

[strouhaljan]

https://github.com/mui/material-ui/assets/11704538/2c486308-7fee-4ffe-99cf-5d991afca2c9

~~Seems like it fails only when interacting with outlined fields for some reason.~~ ^^ Sorry, misleading. It fails when interacting with Country select and Controlled states examples https://mui.com/material-ui/react-autocomplete/#controlled-states https://mui.com/material-ui/react-autocomplete/#country-select

[DiegoAndai]

Thanks for the video @strouhaljan

I still can't repro on Browser Stack, but I'm accepting it as a bug. Hopefully, someone from the community with an Android phone can take a look at it.

[robertkstarr]

Not much to show, but here you go.

https://github.com/mui/material-ui/assets/39703492/22d6a69f-2772-411a-8387-2f6d7a380f7f

[oliviertassinari]

I can't reproduce on Chrome Mobile v121, Samsung S20 FE

• Maybe can be reported in https://issues.chromium.org/issues?q=status:open?
• Can someone check what's going wrong with https://developer.chrome.com/docs/devtools/remote-debugging
• Does it reproduce on https://mui.com/base-ui/react-autocomplete/ too?

[raichshlv]

@oliviertassinari

• Can someone check what's going wrong with https://developer.chrome.com/docs/devtools/remote-debugging

Nothing gets output to the console before the crash. Would adb logcat logs of the chrome process be useful for this?

• Does it reproduce on https://mui.com/base-ui/react-autocomplete/ too?

Yes, what I've noticed is that it happens whenever an element has been highlighted inside the dropdown. (autoHighlight, defaultValue or after setting a value and opening the dropdown again)

[DiegoAndai]

CC @michaldudak. It also seems to be reproducible on Base UI's autocomplete.

[michaldudak]

Thanks for the heads-up. @rstarr-indeed, @raichshlv, does it happen on the Base UI Select as well (https://mui.com/base-ui/react-select/)? If not, the problem should be fixed when we change the Autocomplete implementation to use the Base UI building blocks.

[raichshlv]

Thanks for the heads-up. @rstarr-indeed, @raichshlv, does it happen on the Base UI Select as well (https://mui.com/base-ui/react-select/)? If not, the problem should be fixed when we change the Autocomplete implementation to use the Base UI building blocks.

@michaldudak , The crash does not happen on the Base UI Select component.

[michaldudak]

Since I'm not able to reproduce it locally, we can either rely on a community member to take care of it, or wait (at least a couple of months) until we rewrite the useAutocomplete hook. If you'd like to take a stab on it, I (and I'm sure @DiegoAndai too) can answer questions you may have.

[oliviertassinari]

Can someone report this bug to Chromium? Thanks https://issues.chromium.org/issues?q=status:open

[pecka85]

I have the same issue on my Google Pixel 6 Pro with Android 14 and Chrome 121.0.6167.178.

As requested, I've reported it to chromium. The issue can be found here. 🙂

[pecka85]

Just an update: Since reporting my Chrome has been updated to 122.0.6261.90, and when I test it again now it works fine. 🙂

[robertkstarr]

Working for me as well. I'm going to close the ticket.