-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression in resync speed after being asleep #2425
Comments
(this was on /develop) |
I'm going to accuse matrix-org/matrix-js-sdk#216 of causing this, based on timing and the fact that this will immediately cause it to try & sync again which will take however long a sync takes to time out to time out. |
I just had this again - worse still, it didn't give me any warning I was unconnected; just behaved normally with 24h-stale history until it suddenly popped back into life about 2 minutes after unsleeping my laptop >:( This on current /develop - so vector-web version: vector-f827a2963e82-react-79011886a85e-js-74d6cb802fbe
Whilst we're at it, worth noting this is by far our most regressing bug: #540, #1702 etc. |
haven't seen this since |
I've been getting this for the past hour :/ |
Today and yesterday, it took my vector-web about 95 seconds to wake up after unsleeping my laptop from overnight (Chrome 53.0.2785.116 on OSX 10.11.4). Unsure what has changed, but i'm very surprised we're not seeing 'sync state' console log lines from js-sdk any more saying whether we're in state ERROR or SYNCING etc.
...and then app comes back, without any further console logging?!
The text was updated successfully, but these errors were encountered: