This seems relevant from Chrome development
Chrome dev here. This is related to a new feature that aims to prevent third party software from injecting into Chrome's processes and interfering with its code. This type of software injection is rampant on the Windows platform, and causes significant stability issues (crashes). The Microsoft Edge browser already does this kind of blocking, and we are in the process of making Chrome behave similarly. What you are seeing is the warning phase of year-long effort to enable blocking, originally announced in November 2017.
Since it is effectively impossible for Chrome to automatically determine whether any particular piece of software is innocently injecting or purposefully injecting and interfering with Chrome code. To keep things simple we warn about all injected software, without making value judgments. Note that soon we will actually start blocking software from injecting, at which point this warning will cease to show. Note that you should only be seeing these crashes if you manually navigate to the chrome://settings/incompatibleApplications page, or on a startup after the Chrome browser has crashed.
Additionally, this feature is currently considered experimental so not all users will see these warnings.