chrome no text showing when started in debug from VSCode on Mac - macos

When Chrome starts in debug mode from VSCode not text is displayed. When Chrome is started from from the normal the normal link it displays the site correctly. When the developer tools in Chrome is opened no text is displayed.
Situation occurs since last week.
Google Chrome is up-to-date
Versie 67.0.3396.87 (Officiële build) (64-bits)
I have tried to clear caches and even reinstalled Chrome, but until now no succes.
Image of fault situation Chrome launched from VSCode
Image of desired situation Chrome started normally on same machine

Related

VS Code keeps opening code in Chromium instead of Chrome

I'm trying to open my live server in Chrome but it keeps defaulting to Chromium, no idea why or where it even pulls it from since I only have chrome installed.
Chromium was working at first but it doesn't seem to handle CSS-grid and I need that now.

After using Selenium on macOS, Chrome isn't the same

I installed selenium and used a python program to run chrome using selenium on my MacBook Air. Before there was an error on selenium, and after installing googlechrome drivers for selenium and creating a PATH using terminal, it opened a separate google chrome page that showed Chrome is being controlled by automated test software.
After around 30 minutes of running python and using selenium, I saved and closed out of everything.
In the next 2 minutes, I reopened Google Chrome to search something about web scraping, and the browser was the same one used by selenium. It still showed the Chrome is being controlled by automated test software notice, and there was a Chrome Automation Extension.
I tried:
logging in and syncing, but syncing was not available.
opening Google Chrome from application folder and dock, but nothing changed
deleting Google Chrome and reinstalling, but nothing changed
I don't know how to fix this. Can anyone help me?
Thanks in advance!
Ok, so I found out that the chromedriver was still running in the background. After I closed it using activity monitor, the problem was solved.

SonarQube 6.7.1 freezes on login

This appears to be the same issue as SonarQube 6.7 freezes on login
On mac with Chrome 64 (other browsers don't seem to be affected), with a fresh instead of SonarQube. If I go to the home page (projects?sort=-analysis_date) the page will load everything except the project and end up frozen. (The tab in Chrome itself will be frozen, right click won't work). After 30-60 seconds chrome will have the pop up asking if you want to wait or kill the page.
I tried seeing if anything appear in inspect but i saw no error. If i enter SonarQube from different pages (project pages, admin pages) it works without issue. The freezing only appear on the home page, on mac with chrome 64.

Font issue with Chrome on Mac

I am working on a site where I am having a font issue. The font shows up correctly for all browsers on a PC, but, the issue is when it is viewed with Chrome on a Mac. I know how to do hacks for specific browsers, but, I am at a loss when it comes to Chrome on a Mac. How do you specify for a particular browser on a Mac. I've attached screen captures. Any suggestions on how to fix this? Thank you in advanced for your time and consideration.
Correct Chrome on PC
incorrect Chrome on Mac

Google developer console not loading in Chromium on Debian 7

I am using Debian 7 and Chromium browser.
I'm setting up OAuth authentication via google developer console, but for some reason when I enter https://console.developers.google.com, browser starts loading the page, saying "Waiting for console.developers.google.com" and is stuck forever.
Once in ~7 times it eventually loads the page, but then when I click on any tab, it freezes again.
Anyone experienced something like that?
P.S. On Windows everything's fine.
P.P.S The problem is specific for Chromium browser. Chromium also glitches with google+ notifications - they won't load.
you can try loading Google developer console in privacy mode, meaning opening the console from https://cloud.google.com/ in an incognito window.
"If it works there, it means one of your extensions is causing the security problem and you should remove it." as it explained on the Google Chome Help page :'Fix connection errors.' (Your connection is not private > Tip 2: Try opening the page in incognito mode.)

Resources