-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Crash: "net::ERR_NETWORK_IO_SUSPENDED" after Standby #3102
Comments
same behaviour here:
|
Can confirm this error. Get an identical one! |
I have just had an auto update this morning to 1.21.0 (on Windows) and am got the same error after lunch. This error probably should be caught and ignored, rather than just crashing the app.
|
Same problem here. First time it's happened so far. Bug DescriptionComputer came out of sleep mode and this error was present on the screen. Steps to Reproduce
Actual Result: Signal crashed with error message. Expected Result: Signal resumed operation. ScreenshotsDid not get screenshot - error message attached in txt file. Platform InfoSignal Version: Signal Desktop v1.21.0 Operating System: Windows 10 - latest patches as of 2/6/19 Linked Device Version: Signal on Android 4.32.8 Link to Debug LogPC: Android: |
I am experiencing the same issue. Seems this bug was introduced in the latest version. Everytime I wake my computer from sleep, I see this crash from Signal.
|
Confirmed. |
I've had this both on wake-up and while I was having intermittent network connection issues, so it's just fragile with respect to network unavailability. |
Also experiencing this.
|
I've also run into this error. Error message
|
Got the same exception message (twice) this morning when waking up my PC: Windows 10 64bit, Signal 1.21.0. I'm pretty sure I was updated to 1.21.0 yesterday. |
Can confirm.
|
Same error also.
|
Ditto. Seems to be pretty consistent. Win7, latest version. The bug was introduced in the latest update; it hadn't done it before I updated, so that narrows the attack surface for bug hunters... |
We expect this to be fixed by v1.21.1. Please let us know! |
Seems to be fixed for me - no issues so far. Thanks for working on that! |
I agree, I've not seen this again since updating to 1.21.1, where I encountered the bug often before that update. 👍 |
I've only done it once since the fix, but since it was pretty consistent in previous version, if others are seeing it fixed, I'm willing to call it closeable. |
Bug Description
Signal crashes, if the device has been in standby mode for a couple of hours.
Maybe related to #3097, but since I got a slightly different error (see below), I opened a new issue.
Steps to Reproduce
Actual Result:
Signal crashes with the following message:
This only happens since the recent update to 1.21.0-beta.3.
In older versions, it regularly showed the "No connection. Retrying in 60s" message - probably due to missing network after wakeup.
Expected Result:
Signal should be in normal state. If the network is gone, it should again just show the reconnecting message.
Platform Info
Signal Version: 1.21.0-beta.3
Operating System: Windows 10
Linked Device Version: 4.33.1
Link to Debug Log
https://debuglogs.org/4b0ef0ad9da7cc49dfec609443df9afb804049c06978448b0ff3fac610b49ef9
The text was updated successfully, but these errors were encountered: