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.
Tested again and Orion get's it's first socket disconnect around 20 minutes (plus or minus 2min) from initial load. I don't see any socket disconnect or timeout issues in Safari for the same time period.
@Vlad Let me know if there is anything else that would be helpful to collect.
For reference, I'm running the slack tab with the following settings:
markphilpot Can you confirm in latest RC?
I thought I still had instructions on where to find and download the latest RC but I can't find it -- can you point me to it?
The test above was done with Version 0.99.123.3-beta (WebKit 615.1.16.1)
markphilpot you can find it in #rc-builds in our Discord (provided you have contributor there too, if not ping me)
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.
markphilpot Ok latest beta is out too. These kind of issues usually relate to WebKit. The new version has newer webkit.
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.
markphilpot Best would be to report this to webkit.org, they are very diligent
@Vlad Webkit appears to be the root cause of this issue. @markphilpot should submit this report to webkit.org. A fix will automatically be included in Orion when one is released in Webkit. This issue should be marked as NoFix.
