Chrome 84 is exhibiting stability issues for some people on Android. Whenever they close their last incognito tab, the browser freezes and eventually displays the dreaded "Chrome isn't responding" dialog. The bug seems to bog down the whole interface, as neither home nor back buttons/gestures work while you wait for the popup to appear. Other people even report that Chrome just crashes out of the blue for them, with no incognito tabs involved.
Over the last week, a photo has been making the rounds at venues like Reddit and Twitter. It's an attractive mountain lake with the sun rising (or setting) through the dense clouds. Perfect for a phone's wallpaper, right? Not unless you like bootloops. Certain aspects of the image trigger an inescapable, repeating crash in Android's system UI, and most recent Android phones are likely susceptible, including Samsung phones and Google's Pixels. Thankfully, both Samsung and Google are aware of the issue and looking into a fix.
Chrome on Android has been a bit more crash-happy over the past few months. There were reports of WebView (the Chrome-based engine that powers web content inside apps) having problems last year, and Google has acknowledged Chrome 83 crashes on select Asus devices. OnePlus phone owners have also had to deal with buggy Chrome behavior, as the app has been freezing and crashing on some OnePlus devices for the past several months.
Chrome 83 started rolling out to desktop and mobile platforms earlier this week, and while there were quite a few new features, it seems some bugs also slipped in undetected. The new update has been crashing on some Asus-made phones and tablets, but Google says a fix is on the way.
WebView, the component of Android that renders web pages inside apps (like login screens), is updated through the Play Store. This means that security issues are less of a concern, but it also means bugs can crop up outside of system upgrades. Case in point: an annoying bug is causing web pages inside apps to freeze and crash.
Following a recent update to the Zenfone 6, some owners have been reporting system stability problems including frequent crashes/restarts, network connectivity problems, and bootloops. According to a recent statement issued by an ASUS representative on the company's ZenTalk forums (spotted by PiunikaWeb), the issue is a hardware fault in affected devices which is triggered by the update.
Earlier this week, Google opened a public beta program for its Messages app. I guess we shouldn't be too surprised since this is Google we're talking about here, but the very first Messages beta (v4.7) is instantly crashing on start for most.
For years, Google Maps users begged the navigation service to borrow the incident reporting feature from its peer down the virtual hallway, Waze. But it wasn't until last November that we got a sneak peek at the new option, then a month later, it popped up for many more users. It didn't work at first, was briefly removed, then returned in a functional state. The Maps team isn't content with just crash and speed trap reports, it has recently added a new type of incidents: slowdowns.
Google Maps' incident reporting feature has been a long-time coming. After the company bought Waze in 2013, everyone thought Google Maps would get its popular crowdsourced reporting feature in no-time, but years have passed it's only a few months ago that we started seeing hints of it in our teardowns of Maps. The first real signs started showing up in the app after that, with users spotting confirmation prompts for reported incidents and, recently, a button to report crashes and speed traps. Now, the latter is showing up for many under a new look, but it doesn't work at all.
There's a message that's making the rounds on WhatsApp that mysteriously causes the app to crash if you dare to tap on the black dot within. You may have already come across it and wondered how just tapping on a single emoji can cause an app to freeze and become unresponsive. The answer, unsurprisingly, is that it can't.