As it's an error that happens only in Safari, I suspect an issue in Safari so Apple would have to fix it. I'll report it on my side too.