Intermittently getting "cannot connect" in live preview when reconnecting a previously viewed page

[njx]

I don't have reliable reproducible steps, but quite often on the Mac I seem to have problems reconnecting to live preview, usually after a previous session was closed either by closing the browser or by switching projects or files. The symptom is that trying to restart the connection opens the browser and gets stuck on the "Waiting..." page, and eventually the "Unable to connect" dialog shows up in Brackets.

Will continue trying to repro, but wanted to file this in case others are seeing it.

[marcelgerber]

I'm getting such a bug quite often as well (I have to say, I don't use live preview very often), but I dunno if it is this bug or #5687 - they seem pretty similar.

[redmunds]

I also saw this today on Windows 7, but I was testing the shapes extension, so I thought it was related to that.

[pthiess]

@ingorichter: Please take a look at this when working on #5687, as @SAplayer pointed out this might be related.

[oslego]

I'm also getting this intermittent bug quite often on Mac. It occurs seemingly at random, even with extensions turned off.

[redmunds]

When I see this error it's usually a timeout. One thing to try: when Live Preview is first opened in a new instance, open a second tab and leave it open. This makes switching Live Preview sessions faster because Chrome doesn't need to close and re-open browser window -- only close and re-open a tab within window.

Of course, this isn't a final solution, but if this seems to fix problem, then maybe we just need to increase timeout wait time.

[njx]

The thing that usually seems odd to me when I encounter it is that it doesn't look like the page is timing out - it usually loads fully in the browser and appears fine long before the timeout error appears. So it seems like somehow we're not getting (or are incorrectly processing) some event that tells us the page is loaded and everything's good.

[marcelgerber]

@njx This is exactly the thing I see. Chrome is opened, the page (HTML + CSS) is fully loaded, and 5 or 10 seconds after that the error message appears (there was definitely enough time to get the Chrome event).

[njx]

Nominating.

[njx]

Duping out to #5687 so @ingorichter can look at it at the same time.