This repository has been archived by the owner on Jul 6, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 57
Error in socketOnTimeout #179
Comments
Looks like destroy is happening before the timeout, we need to make sure that destroying clears the timeout to avoid the issue here. |
Think I have this one and in the process fixed another issue. |
Great, I'll give it a try! Will reopen if I find any issues. Thanks for this. Been meaning to write that compat documentation but haven't had much time this week because we bought a new place. Learning a lot about plastering walls though. 🤷♂️ |
jasnell
added a commit
to nodejs/node
that referenced
this issue
Aug 4, 2017
Fixes: nodejs/http2#179 Was fixing issue #179 and encountered a segault that was happening somewhat randomly on session destruction. Both should be fixed PR-URL: #14239 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
jasnell
added a commit
to jasnell/node
that referenced
this issue
Aug 13, 2017
Fixes: nodejs/http2#179 Was fixing issue nodejs#179 and encountered a segault that was happening somewhat randomly on session destruction. Both should be fixed PR-URL: nodejs#14239 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
addaleax
pushed a commit
to nodejs/node
that referenced
this issue
Aug 14, 2017
Fixes: nodejs/http2#179 Was fixing issue #179 and encountered a segault that was happening somewhat randomly on session destruction. Both should be fixed Backport-PR-URL: #14813 Backport-Reviewed-By: Anna Henningsen <[email protected]> Backport-Reviewed-By: Timothy Gu <[email protected]> PR-URL: #14239 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm getting some real-world traffic on my server and it occasionally throws these uncaught errors. Seems to be related to the socket timeout.
The text was updated successfully, but these errors were encountered: