Mother's physical therapy, and Google Chrome woes
13 years ago
General
Well, my mother was finally discharged from the hospital...to a nursing home to continue her physical therapy. I've visited her there, and she's still settling in and they are still preparing her therapy plan. She still can't swallow, but she can...sort of talk. Only some of her words can be understood. Her mental faculties are all there, but she still has trouble talking and writing. Therapy will continue to work on that.
Aaaaaaaaaaaaaand...Google Chrome has stopped working entirely, and I don't know why. The browser window opens, but the tabs are stuck in "Loading" and never open a page - Process Explorer showed me that the main Chrome.exe process was failing to spawn child Chrome.exe processes as it normally does. Other browsers work fine. I did a full update of Avast Anti-Virus and did the deepest possible scan (5 hours long), and it turned up nothing. Changing the Google Chrome commandline settings to include the switch "-no-sandbox" allows it to work again, but I don't want to browse it without any security settings. I'd been having repeat crash problems already, but this now makes Chrome just about unusable. Googling for forums doesn't provide much help, as this problem has been acknowledged as far back as 2009 and it seems like no one can agree on what causes it or how to fix it. Someone suggested that it's not an external problem, but a serious bug within Chrome itself that arises from a poorly implemented plugin mechanism. I honestly don't know what to think. But for now, I'm writing this journal in Firefox. Sometimes I use Safari too. The main attraction of Chrome was its speed and ability to juggle many tabs at once with relative elegance, but the repeat crashes and now its failure to load just might make me abandon Chrome for good.
Aaaaaaaaaaaaaand...Google Chrome has stopped working entirely, and I don't know why. The browser window opens, but the tabs are stuck in "Loading" and never open a page - Process Explorer showed me that the main Chrome.exe process was failing to spawn child Chrome.exe processes as it normally does. Other browsers work fine. I did a full update of Avast Anti-Virus and did the deepest possible scan (5 hours long), and it turned up nothing. Changing the Google Chrome commandline settings to include the switch "-no-sandbox" allows it to work again, but I don't want to browse it without any security settings. I'd been having repeat crash problems already, but this now makes Chrome just about unusable. Googling for forums doesn't provide much help, as this problem has been acknowledged as far back as 2009 and it seems like no one can agree on what causes it or how to fix it. Someone suggested that it's not an external problem, but a serious bug within Chrome itself that arises from a poorly implemented plugin mechanism. I honestly don't know what to think. But for now, I'm writing this journal in Firefox. Sometimes I use Safari too. The main attraction of Chrome was its speed and ability to juggle many tabs at once with relative elegance, but the repeat crashes and now its failure to load just might make me abandon Chrome for good.
FA+

Now, I just go back and forth between Firefox and Opera; what doesn't work in one, will usually work in the other.