Hi, thanks for reporting this issue! The team has been able to reproduce the problem on one of our testing devices and is investigating it now. We are not sure yet, whether this is a Chrome bug or an AMS bug.
But as we scan the web before the loading gets stuck, it might be that the Chrome/Web page code somehow conflicts with accessibility service. So it seems improbable we are causing this, but we need to double-check, which will probably take some time. Thanks for understanding.