Update:
As of the comment by morficus, the problem has been fixed in the version: 4.0.1
The plugin will auto-update or you could reinstall from here:
https://chrome.google.com/webstore/detail/wappalyzer/gppongmhjkpfnbhagpmjfkannfbllamg
If anyone is interested in the issue the pull request is here:
https://github.com/AliasIO/Wappalyzer/pull/1491
2019 Edit:
If that is not solving your issue. You could try disabling all the chrome extensions and check if that solve your issue.
To disable you could type the below code in chrome url:
chrome://extensions/
or could go on
Settings > Extensions
After that you could enable each extensions and check the culprit.
Older issue:
It is not the chrome’s bug but the bug with the wappalyzer extension.
I am not sure you are using it but i have used it and was just updated and got the same issue.
Here is the proof of the issue:
https://github.com/AliasIO/Wappalyzer/issues/1487
We need to wait until there is any solution for the extension or use the older version of the extension until it gets resolved.