Google Chrome, Microsoft Edge: Issues on MacOS

Well, I much rather vent my frustration on this post than surrender to insanity.

Up until a couple months ago, I was running Google Chrome normally as my primary browser, due to integrations with work tools.

All of the sudden, I started to experience unresponsive tabs and windows within Chrome once my MacBook was closed then opened and/or woke up from sleep, which meant it had to disconnect and connect to a wifi network (even if it was the same network).

The issue didn't stop there. I had to force quit Chrome, but it would remain in that unresponsive state upon relaunch, so once again I had to force quit it, and now restart my computer. Also, restart didn't go through normally, I had to keep the power button pressed and then press it once again to turn my Mac on.

So, upon much navigation over the Internet, I found literally hundreds of posts with possible solutions, and one by one tried them to no avail. I even updated to Catalina (from Mojave 10.14.6) even though I needed a bunch of 32bit apps, which have been rendered obsolete.

Eventually, I decided to give up on Chrome and try Microsoft Edge, which is Chromium based. Well... wait for it... Same BS!

Tried paid solutions to see if it was a virus, erasing profiles from Application Support, using a VPN, Proxy, etc. ****, I even got my Mac to an exorcist!

I now got back to Safari, will log in to Google and make it work with my work tools, no problem.

The real issue here is the accountability from Google and Apple has rounded up to 0... I've been a Mac user for over 25 years and used to love the overall quality of the products, not only from the physical standpoint but for their usability and reliability.

Now that is all gone. I expect that type of behavior from a monster company like Google, with no time to address issues that undermine user productivity, but Apple used to be different, TO THINK DIFFERENT!

Any how, all thread with this issue, from the last year or so, seem forgotten. On Chrome support they are even locked and closed for comment. I hope this helps to shine a light on this annoying issue and we can find a workaround as a community.