This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
Double-free of parser from FreeList in http.js #803
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the documentation, a socket
error
event will be followed by a socketclose
event. However, the HTTP Agent frees its parser on both events, causing the same parser reference to be pushed twice to the FreeList. This causes strange behavior down the road on further requests, and even HTTP server requests are affected by it.This patch fixed for us what's been seen in the following discussion: https://groups.google.com/d/topic/nodejs/kYnfJZeqGZ4/discussion
Possibly related issue: #784
The patch on top of v0.4 is at: https://github.com/AngryBytes/node/tree/v0.4-parser-fixes