Fix infinite loop when the connection closes partway through a bulk reply - #1731
Open
NotAFlightRisk wants to merge 2 commits into
Open
NotAFlightRisk wants to merge 2 commits into
NotAFlightRisk wants to merge 2 commits into
Conversation
tillkruss
requested changes
Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fread()gives back an empty string at EOF rather thanfalse, so when the connection closes partway through a bulk reply, predis keeps waiting for bytes it'll never recieve and pegs a core until you kill it.read_write_timeoutdoesn't help because every read returns straight away.You don't need anything exotic to hit it. A pubsub subscriber that falls behind gets cut off by Redis's default
client-output-buffer-limit pubsub 32mb 8mb 60, and when the cut lands in middle of a message the subscriber on 3.6.1 just spins. Killing Redis during a bigGETdoes the same.Both connection classes had the same loop, so both now throw the usual
ConnectionExceptionwhen a read comes back empty at EOF, same as a close between replies already does. The tests are most of the diff, the fix itself is a few lines in each class.