What the Chrome ‘5 Windows’ Crash Bug Is
The Chrome ‘5 windows’ crash bug is a fault in Chrome version 148.0.7778.178 on Android tablets that causes the browser to fail on launch, showing a message about a five‑window limit and then immediately closing, even when no other Chrome windows appear to be open. Users tap the Chrome icon, see a brief prompt saying “You can have up to 5 windows,” and are dropped straight back to the home screen with no chance to access tabs, settings, or history. According to Android Authority, this behavior is tied to Chrome’s latest update and is severe enough that it “can completely lock users out of the browser.” Because the error repeats every time Chrome starts, the app becomes unusable as a daily browser until you change versions or switch to an alternative.
How Widespread the Problem Is and Who Is Affected
Reports from Reddit and the Chromium Issue Tracker show Chrome crashing on launch across many Android tablets, not a single brand. Samsung models like the Galaxy Tab S9 FE, Tab S6 Lite, and Tab A11+ appear most often, but Lenovo Tab M11 and Xiaomi Pad 6 owners are also seeing the same Chrome 5 windows error. Android Police notes that it persists even when no other apps are open and after standard troubleshooting like clearing cache, force stopping Chrome, or rebooting the tablet. DigitBin describes Chrome 148.0.7778.178 as “crashing on launch across multiple Android tablet brands with a spurious ‘5 windows’ error.” The issue cuts across different Android versions and memory configurations, which points to a bug in Chrome’s tablet build rather than any one manufacturer’s software or hardware setup.
Why Chrome Is Miscounting Windows and Crashing
Early developer discussion, summarized by Android Authority and DigitBin, links the bug to Chrome’s newer, more desktop‑like multi‑window behavior on Android tablets. Recent builds allow separate windows for features like incognito, instead of keeping everything inside a single Chrome instance. On some lower‑memory tablets, Chrome appears to lose track of these standalone windows after they close. The browser keeps a hidden count of sessions that no longer exist, assumes the user has already hit the five‑window cap, and refuses to open a fresh window. That five‑window limit is meant as a stability safeguard, but here it is firing when the real window count is zero, triggering the Chrome crashing Android tablets problem. DigitBin reports that engineers are examining changes that could disable this incognito standalone window behavior on tablets below certain RAM thresholds, though no fix has shipped yet.
Google’s P1 Response and What It Means
Once user complaints began to pile up, Google acknowledged the issue publicly through a verified Chrome Support Manager on Reddit. The representative asked affected users to share their Android build number, device model, Chrome version, and any active window counts to help the engineering team pinpoint the cause. DigitBin confirms that Google has classified the bug as a P1 priority on the Chromium Issue Tracker, which means it is treated as a high‑urgency problem within the Chrome project. This level of priority usually indicates that a fix is being investigated for rapid release, potentially as a minor patch update. Until that patch rolls out through the Play Store, however, the current Chrome 148 build may remain unusable on many tablets, leaving users dependent on older versions or other browsers to get back online.
Workarounds: Temporary Android Tablet Browser Fixes
Until Google ships a patch, there are two main ways to work around Chrome not opening on your tablet. The only confirmed in‑Chrome fix is to roll back the app to its factory version. In Android settings, open Apps, find Chrome, tap the menu, and choose “Uninstall updates.” This removes version 148.0.7778.178 and restores the older build that shipped with your device, which users say opens normally again. Sign back into Chrome to restore synced bookmarks and passwords, but expect to lose any unsynced local tabs. To avoid the problem returning, disable auto‑updates for Chrome in the Play Store until news of a fix appears. If you would rather not change settings, switch to an alternative browser such as Firefox, Edge, or another privacy‑focused option as a temporary daily driver while Google resolves the Chrome 5 windows error.