Review the following articles:
- Configure Chrome & Firefox for Web Automation
- Using Chrome Web Extension with Multiple Chrome Profiles
Possible cause #1
Possible cause #2
Reinstalling the add-on sometimes will fix this issue as well, usually happens in Chrome browsers that have multiple extensions installed.
Possible cause #3
It is important to note that this issue can be hardware-related. Hence, if it persists, then this possibly means that the machine's hardware resources are limited.
Possible cause #4
The Robot may not have enough permissions to interact with Chrome. In order to check if this is the problem, run Process Studio with administrator rights. If this resolves the issue, then configure your Robot to run as admin as well. Check this article.