Thomas101
commented
10 months ago Hi, thanks for reporting. Would you be able to reach out to support@wavebox.io? We can generate some diagnostics and see if we can get to the bottom of this. Thanks!
Open moorecp opened 10 months ago
Thomas101
commented
10 months ago Hi, thanks for reporting. Would you be able to reach out to support@wavebox.io? We can generate some diagnostics and see if we can get to the bottom of this. Thanks!
postwait
commented
10 months ago I am also encountering this. Seems isolated to Slack at this point.
Thomas101
commented
10 months ago Thanks @postwait. We haven't been able to reproduce it here yet, could you message support@wavebox.io? Hopefully we can figure out what's causing this
mmoore-3lc
commented
10 months ago Been getting this as well on Edge and Chrome (both Chromium browsers).
bagarwa
commented
10 months ago fwiw, I'm also getting this error for my workplace's slack when trying to access it on Chrome or Edge. (I'm not a wavebox user. This issue popped up in my google search when I was googling that error.)
Thomas101
commented
10 months ago @mmoore-3lc @bagarwa thanks so much for commenting in! Do you know which version of Chrome & Edge you're using? Also are you able to give a list of extensions that you have installed? Thanks!
mmoore-3lc
commented
10 months ago @Thomas101
Chrome: 119.0.6045.124 Extensions: Lastpass 4.123.0, Raindrop.io, DarkReader, 1Password, Adblock, Fakespot, Loom, Node debugger, TamperMonkey, Always Clear Downloader, History Trends, History Trends Unlimited, Trello Cards Optimizer, Unhook - Remove YouTube Recommended Videos, Zendesk Quicktab
...now, excuse me while I remove some of these....
Thomas101
commented
10 months ago It might also be worth updating Chrome, 119.0.6045.159/160 shipped last night. This version of Chromium is running through our build system for Wavebox at the moment so can't confirm if it fixes the problem.
mmoore-3lc
commented
10 months ago Thanks for the heads up. Updated, same issue, hope that helps
DeeJ
commented
10 months ago Getting this on Chrome 119.0.6045.124 & 119.0.6045.160
habinpark
commented
10 months ago Currently a problem on edge as well
bagarwa
commented
10 months ago Slack is now back to working on my Windows 11 Chrome Version 120.0.6099.28 (Official Build) beta (64-bit).
moorecp
commented
10 months ago EDIT: I take it back. It works sort of sometimes, then stops working with the same error.
Original Message: Slack is now working again in my same Wavebox build on Windows 11. Must have been Slack's problem to fix as opposed to Chromium.
Thomas101
commented
10 months ago Thanks @moorecp, from what we've seen users who are affected see the same issue across Chromium browsers on the same machine. We're working to move Wavebox across to Chromium 120.0.6099.28 as other people have reported this seems to resolve the issue. All being well it should hit our beta channel early next week 👍
Thomas101
commented
10 months ago Hi, we've just pushed Wavebox 10.120.3 to the Wavebox beta channel, this is updated to Chromium 120.0.6099.28 so hopefully will fix the issue. If it does/doesn't, it would be great to know!
moorecp
commented
10 months ago Hi, we've just pushed Wavebox 10.120.3 to the Wavebox beta channel, this is updated to Chromium 120.0.6099.28 so hopefully will fix the issue. If it does/doesn't, it would be great to know!
All of my Slack workspaces work correctly on the new Beta release. :shipit:
Thanks!
Thomas101
commented
10 months ago Yay! Thanks for letting me know.
For anyone who doesn't want to use the beta, we're expecting it to move across to the stable channel sometime during the week of the 4th of December 👍
Bug/Feature description
After updating my Windows 11 install to 10.119.8.2, all 3 of my Slack groups give me a Chromium error page.
If I inspect the network traffic, I see a GET request to
https://app.slack.com/client/<server>/<channel>that returns a 200, but then Chromium throws that STATUS_ACCESS_VIOLATION error. I've tried clearing the cookie containers which allows me to log back into the Slack workspaces, but leads to the same error. Visiting the workspaces via the Slack mobile app and Firefox both work as expected.