Most likely, there is some sequence of events fired during loading a page that Chrome produces and WWW::Mechanize does not cater for.

The interesting events usually start with Page.frameScheduledNavigation, Page.frameStartedLoading or Network.requestWillBeSent. Maybe some resource is now retrieved from cache and some event is not fired when the module expects it to be fired.

Without seeing the sequence of events, this is hard to track down. I'll try your script later and see if I can reproduce it.

What version of WWW::Mechanize::Chrome and what version of Chrome are you using?