I have met this problem yesterday. It's because of the server didn't response some resources.
In my page, i have some large file links like<a href="/file_path">file_name</a>
,
and this happend only in chrome.
In a while ,I recognized this maybe caused by the chrome's 'Predict network actions to improve page load performance' feature.So I turned off this feature in chrome://settings
and try it again. As expected, the error didn't occur again.
After that, I changed resource links with full_url_path instead of relative_path(in rails, use resource_url instead of resource_path), then I didn't have to turn off the chrome's feature. And it looks good.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…