I've seen this when we tests logged in users and on my test server where I test a couple of Wikipedia pages after each other. The problem is like this: When we test with Chrome sometimes (not often) taking a screenshot fails, and after that, the navigation to the next page takes a really long time, making it timeout.

I've been able to reproduce this on my local machine and I could see in the Chromedriver log that the navigation happens in JS but the actual Page.frameScheduledNavigation takes long time to happen. Comparing to other pages in the "flow" when screenshot not fails, the navigation happens direct. But I'm not sure if the screenshot is the problem or if its something else.

I've created an upstream issue: https://bugs.chromium.org/p/chromedriver/issues/detail?id=3307
And has been problem with screenshot hanging forever if an alert fires but we don't fire any alerts.

Not sure also if this was introduced with Chromedriver 79? At our we rollbacked to 78 and when I briefly looked at the log I could see anything (but I remember seeing before) but we also has some other errors to take care of, the log is quite noisy at the moment.