What the Chrome 148 Android tablet bug is and how it looks
The Chrome 148 Android tablet bug is a software error in version 148.0.7778.178 that causes the browser to crash immediately on launch, falsely claims users have reached a five‑window limit, and prevents any access to Chrome until the app is downgraded or patched by Google. When affected users tap the Chrome icon, the app tries to open, flashes a message saying “You can have up to 5 windows,” and then drops straight back to the home screen in under a second, even if no other Chrome windows are open. Reports highlight a widespread Android tablet crash pattern that ignores usual troubleshooting steps like clearing cache, deleting data, or rebooting. According to Android Authority, Google has now acknowledged the Chrome 148 bug and elevated it internally as a top‑priority issue.
Which tablets are crashing and why the ‘5 windows’ error appears
The crash is linked specifically to Chrome version 148.0.7778.178 on Android tablets and has been heavily reported on Samsung Galaxy Tab S9 FE, Tab S6 Lite, and Tab A11+ models, with Lenovo Tab M11 and Xiaomi Pad 6 users also seeing the same ‘5 windows error’ before the app closes. This means the issue is broader than a single tablet brand or Android build. According to DigitBin, developer discussion points to Chrome’s newer desktop‑style multi‑window features on tablets, including separate incognito windows, as the likely cause. On some lower‑memory devices, Chrome appears to keep a “ghost” count of closed windows and incorrectly believes the five‑window limit has already been reached, so it refuses to open a new session and triggers an Android tablet crash loop instead.
Urgent workaround: Chrome lockout fix you can apply right now
Until Google ships a patch, the only Chrome lockout fix that consistently works is rolling Chrome back to its factory version by uninstalling updates. On most Android tablets, open Settings, go to Apps, find Chrome, tap the menu (three dots) and choose “Uninstall updates.” This reverts Chrome to the version that shipped with your device before the 148 update and should stop the instant Android tablet crash on launch. Your synced data such as bookmarks and passwords will return when you sign back into Chrome, but any unsynced local tabs from your most recent session will be lost. After rolling back, open the Play Store, find Chrome, and disable auto‑updates so the buggy 148.0.7778.178 build does not reinstall in the background and lock you out again.
Google’s response and what to use while you wait for the patch
User complaints on Reddit were quickly escalated to the Chromium Issue Tracker, where a verified Chrome support manager asked for Android build numbers, device models, Chrome versions, and window counts to help engineers track the Chrome 148 bug. Google has tagged it as a P1 priority, meaning the crash is treated as a blocker for core browser use and should be fast‑tracked into the next Play Store release once a fix is ready. There is no confirmed release timing yet, so keep an eye out for an update newer than 148.0.7778.178. In the meantime, you can stick with the rolled‑back Chrome build or switch temporarily to an alternative browser such as Firefox for Android or Samsung Internet, both reported as stable options that keep everyday browsing usable on affected tablets.
