There has been significant progress made on this issue recently by the Chrome team. Incidence rates of the error have fallen significantly and fixing the problem no longer requires killing the Chrome process -- a browser refresh is sufficient. The underlying cause is an open bug with Apple and is not yet resolved.
To see these improvements, please update to the latest version of Chrome.
For more details, you can find the related bugs linked below. The first link includes video links that go into further detail about the changes.