-
-
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_NAME_NOT_RESOLVED" #3097
Comments
Can you talk about your network? What network state are you in when this happens? Does it happen whenever you're offline, or when your DNS provider is having problems? |
I got something similar recently when I opened my Mac without a wifi connection with Signal still open in the background.
|
@scottnonnenberg-signal I also experienced something similar. Please tell me if you want to make a new issue or if you want it here.
Immediately after starting Signal after the crash, I received a "A new version of Signal is available" message so if I had to guess, this is an issue with the updater. This has never happened before. |
Bug descriptionSince updating to v1.21.0 I get the following error from Signal desktop every time I wake my system (WIndows 10) from overnight sleep. It never happened in previous versions. It appears that the system needs to be asleep for some time. Just putting it to sleep and waking it right back up doesn't reproduce the issue. Based on
Steps to reproduce
When the system wakes up, a dialog with the above error message is displayed, and the Signal window is gone. Device info
|
I am having a similar crash on startup issue. Clean install of 1.21.0 on Windows 10 pro. I am having issues attaching the log file for some reason.
|
We expect this to be fixed by v1.21.1. Please let us know! |
Ya, seems fixed now. Ip firewall blocks packets but Signal Desktop is not
crashing. Nice.
…On Fri, Feb 8, 2019 at 4:39 PM Scott Nonnenberg ***@***.***> wrote:
We expect this to be fixed by v1.21.1. Please let us know!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3097 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APg9sxEpDDNBtcU_WotY5KkPCiL_tuQtks5vLe50gaJpZM4adaM_>
.
--
PikesvillePC.com
This email may contain privileged and/or confidential information that is
intended solely for the use of the addressee. If you are not the intended
recipient or entity, you are strictly prohibited from disclosing, copying,
distributing or using any of the information contained in the
transmission. If you received this communication in error, please contact
the sender immediately and destroy the material in its entirety, whether
electronic or hard copy.
TLP:WHITE
|
This bug seems to have resurfaced with these ip's causing a crash:
13.33.165.209
13.33.165.227
13.33.165.209
13.33.165.227
13.33.165.209
13.33.165.227
…On Mon, Feb 11, 2019 at 2:47 PM Scott Nonnenberg ***@***.***> wrote:
Closed #3097 <#3097>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3097 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APg9s7dmwutCt31YI6t67eREwbRDo7CKks5vMcjAgaJpZM4adaM_>
.
--
PikesvillePC.com
This email may contain privileged and/or confidential information that is
intended solely for the use of the addressee. If you are not the intended
recipient or entity, you are strictly prohibited from disclosing, copying,
distributing or using any of the information contained in the
transmission. If you received this communication in error, please contact
the sender immediately and destroy the material in its entirety, whether
electronic or hard copy.
TLP:WHITE
|
@n31n The ips really aren't important. What is important is the actual error callstack, specific version numbers, a debug log from your client, etc. |
Yes, sorry. Here is a link to the log. This crash only happened once, so
far, and oddly, Signal updated less than a minute after I posted this last
night.
https://debuglogs.org/9ec5f245da08749a23587f91a3b23552e779978477e36644e0a6ed19cd9d48ba
…On Wed, Feb 13, 2019 at 12:34 PM Scott Nonnenberg ***@***.***> wrote:
@n31n <https://github.com/n31n> The ips really aren't important. What is
important is the actual error callstack, specific version numbers, a debug
log from your client, etc.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3097 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APg9syTbeOncbiIdWBsDLpllzqHdZER2ks5vNEykgaJpZM4adaM_>
.
--
PikesvillePC.com
This email may contain privileged and/or confidential information that is
intended solely for the use of the addressee. If you are not the intended
recipient or entity, you are strictly prohibited from disclosing, copying,
distributing or using any of the information contained in the
transmission. If you received this communication in error, please contact
the sender immediately and destroy the material in its entirety, whether
electronic or hard copy.
TLP:WHITE
|
@n31n Cool, thanks. Please also paste what you saw in the error dialog before it crashed. The specific callstack is important to help us track down the source of the problem. |
I missed that error log. If it happens again I will post it.
…On Wed, Feb 13, 2019 at 12:44 PM Scott Nonnenberg ***@***.***> wrote:
@n31n <https://github.com/n31n> Cool, thanks. Please also paste what you
saw in the error dialog before it crashed. The specific callstack is
important to help us track down the source of the problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3097 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APg9s_azWF_oZUdnP_fh7tHPQ8svqbogks5vNE8TgaJpZM4adaM_>
.
--
PikesvillePC.com
This email may contain privileged and/or confidential information that is
intended solely for the use of the addressee. If you are not the intended
recipient or entity, you are strictly prohibited from disclosing, copying,
distributing or using any of the information contained in the
transmission. If you received this communication in error, please contact
the sender immediately and destroy the material in its entirety, whether
electronic or hard copy.
TLP:WHITE
|
Here is the error dialog that i'm getting, similar issue it looks like.
|
Bug Description
Screenshots
Platform Info
Signal Version: 1.21.0-beta.3
Operating System: Windows 10
Link to Debug Log
https://debuglogs.org/e804836ed54f6758ef4f2306faf00cb2a790b01b3594b79871bd0150ac476fa2
The text was updated successfully, but these errors were encountered: