In my case the error was caused by a Chrome extension. The ID of the extension was part of the error message in the browser console, so it was easy to find out which extension was causing the issue on the Manage extensions page. After the extension was removed, the issue disappeared.