31–40 of 86 posts
On XiaoMi phones at least, this is a system app (see: bloatware). That means you can't clear its app data nor uninstall it, effectively bricking Chrome permanently. The only thing you can do is uninstall the updates, which force resets its persistence, losing all of your stored data/sessions. If you've already done that... tough luck, I guess? What an awful bug.
On XiaoMi phones at least, this is a system app (see: bloatware). That means you can't clear its app data nor uninstall it, effectively bricking Chrome permanently. The only thing you can do is uninstall the updates, which force resets its persistence, losing all of your stored data/sessions. If you've already done that... tough luck, I guess? What an awful bug.
I did this and was so furious the phone was bricked i threw my phone out a train window.... Was i too soon?
Earlier quoted context omitted.
Off Topic: I don't get it why, after 10 years of mobile browser development, there still is no "close all tabs at end" option. Every time I visit my parents, I have to clean up their 150+ open chrome android tabs because they don't understand how to properly clean up their browsing sessions. Why on earth would I want to open the same old tabs in the morning, that I already looked at the day before?
Because they are the tabs with your email, facebook, news, and and and.
maybe you need to be not in incognito? i didn't want to test out of it in case it actually bricks my browser
Earlier quoted context omitted.
You realize "safe" languages don't protect you from all bugs, right? So tired of this narrative on HN.
But actual crashes are most likely due to memory unsafety; I’d be extremely surprised if the root cause was not found to be in a memory-unsafe language, though I doubt it’ll be in the URL parser.
But in Rust, something like this could happen too, if someone added a panic!, e.g. on parsing a domain name with an empty component, or failure to put the domain name in a certain (external) structure. If the URL is parsed again on start-up, the application would be bricked. Granted, it's much easier to find and solve.
My bet is on url parser in unsafe language
My bet is URL parser with insufficient tests. It is well known that URLs are hard; nobody should ever trust their own implementation of a URL parser unless it is sufficiently tested (payload repositories exist for a reason).
(I don't do any bets thought, sorry)
On XiaoMi phones at least, this is a system app (see: bloatware). That means you can't clear its app data nor uninstall it, effectively bricking Chrome permanently. The only thing you can do is uninstall the updates, which force resets its persistence, losing all of your stored data/sessions. If you've already done that... tough luck, I guess? What an awful bug.
The base .apk is stored on a read-only system partition, so you can't completely get rid of it, but typically you should be able to remove all data of that app, clear its cache, uninstall any updates it downloaded (since those are stored on another partition), and also disable it.
I haven't used any OS by Xiaomi in a while, so I don't know if they changed anything about that.
Though I used to run their MIUI OS on my Samsung Galaxy (S2 or S5, I don't remember) for a while. That one was the opposite of locked down and even shipped pre-rooted, but it's been a long time.
On XiaoMi phones at least, this is a system app (see: bloatware). That means you can't clear its app data nor uninstall it, effectively bricking Chrome permanently. The only thing you can do is uninstall the updates, which force resets its persistence, losing all of your stored data/sessions. If you've already done that... tough luck, I guess? What an awful bug.
Edit - quick googling says Xiaomi have their own browser as default / system, is that what you're referring to?
Earlier quoted context omitted.
You realize "safe" languages don't protect you from all bugs, right? So tired of this narrative on HN.
But actual crashes are most likely due to memory unsafety; I’d be extremely surprised if the root cause was not found to be in a memory-unsafe language, though I doubt it’ll be in the URL parser.