f-stop
Active Member
my experience with the browser the past several months seems the same.I’m still on 32.11.1 and the browser dies on its own (without even using it) in about 24h after a reboot. I find it a pity as when it works, it’s still slow but useful.
I have not had 32.12.2 proposed yet but if it does not help on that issue, i’ll just wait for the next one.
I received 2019.32.12.2 a few days ago (70D, MCU1/AP1) - after the first couple days I thought the browser was working normally again (by "normally", I mean to say it seemed back to its pitifully slow glacial self it always used to be i.e. very slow but at least it seemed to be working without randomly dying)
but it was too good to be true, the 3rd day after receiving 32.12.2 the browser is back to not working - i.e. the browser window stays blank - typing in a URL or clicking on a favorite does nothing - no progress bar movement, no sign of life at all.
Prior to the update a few days ago I was on 2019.32.11.1 and for that version through back a number of updates to one of the early v9 releases (sorry I forget which), my browser would work for at most a day and then die. reboot would temporarily solve it, but sometimes later in the same day or at most a day later it would stop working again, even if I wasn't using it in between. So, no forward progress with 32.12.1 for the browser problems, it seems... BTW the 32.12.1 release notes didn't seem to have any differences from those for 32.11.1