Waiting for available socket

Targets Web
1

I have been working with WE on a Mac for a week or so and am puzzled by the variability of response times when running the app in the IDE on Chrome.

It started by ProgressBars and Image Well not loading right away. The rest shows immediately, though, but it takes up to ten seconds for these two controls to show. With no real consistency. Sometimes it loads right away, sometimes not. Strangely enough, it seems setting focus to the IDE somehow triggers the display. Apparently, execution is somehow halted as well, and I have a routine that takes between 0.1 second up to 7 as the result. In spite of pragma DisableBackgroundTasks.

Most amazingly, it does not happen at all in Safari, where loading is immediate and consistent.

I suspected extensions, but even after disabling them all, this still happens.

I have not yet tried placing the app on a server, but that is quite annoying. Chrome has many users.

2

I’ve noticed this as well while debugging a WE standalone app on Windows 8.1 in Chrome. It looks like the application randomly stops in the IDE if I don’t interact with it in the browser for 10 seconds or more. I don’t have this issue with a built application running locally or on a server.

3

I was concerned, since it is the first time I noticed that. It maybe due to the number of controls on the page.

I have switched to Safari, though.

Thank you for reassuring me it was not some glitch here.