Slack stops updating

Well I can confirm that it's not Low Power Mode (that is definitely off).

I will leave the dev console open on the slack tab for a bit and see if I can see anything. It definitely involves time and possibly leaving the tab open but unfocused, but it doesn't happen immediately when taking those steps.

I'll add more details as soon as I can narrow it down a bit.

So this very well could be a bug with slack but it definitely is websocket related and I don't see it in other browsers. Looking at the console logs (which Slack has in abbundance), after leaving the laptop with display long enough to trigger the "reenter password" state, the websocket isn't able to reconnect (though looking at the console logs it's definitely trying).

I'll need to do a side by side comparision with Firefox or Chrome to compare the log output. For now, I'm upload a text copy of the console logs.

Ok, so I had a reason to run Slack in Orion side by side with the desktop app to see when things started to go stale. It is indeed websocket related...

After some disconnects, from the info logs it looks like it's able to reconnect.

But for what ever reason, it gets into a situation where it seemingly can't reconnect.

For my next test I'll try doing a side by side comparison with Safari directly.

Ok here is the console output of the same Slack workspace showing Safari on the left and Orion on the right.

We see that after on a few minutes open (I think about 20) -- Orion (on the right) starts having trouble with the socket connection.

I'll re-run the same test shortly to see if th timing is repeatable, but there is definitely something going on in Orion's websocket handling that isn't present with Safari.

So I've been testing for the last hour and not seeing the websocket errors!

I'll let it run overnight and report back tomorrow (hopefully with good news)

At about 2 hours with the tab open, slack stopped updating. There was an instance of the same timeout

For whatever reason it took longer to manifest this time. Tomorrow I'll do the same side-by-side comparison with Safari.

Ok, did side by side with Safari and Safari also became stale and refused to update with the same set of websocket timeouts and disconnects (just in different timeframes).

I think you're right and this is root WebKit related and not any of Orions customizations.

I'll try to do a side by side comparision with Safari anytime Orion or Safari get updated, just to keep track of this ongoing issue.