I can actually reproduce this right now in Chromium on arm64 Linux. Chromium 125.0.6422.76, no error messages in the developer console when this happens. Still, interesting that (I think?) all these reports have been from Chrome/ium on arm64 platforms... I wonder if we're triggering some architecture-specific browser bug?