Repository navigation
Don't leak kept scanner state in loose parser - #379
Merged
Merged
Conversation
GitHub: Fix rubyGH-378 Since CSV#shift re-enters CSV::Parser#parse for each row, parse_quotable_loose left one keep per row in the scanner. Each keep retains a StringScanner and its chunk. A keep was also leaked when an exception was raised while parsing a row. If the caller rescued it and continued reading from IO, every following keep_drop merged its buffer into the leaked keep. Use ensure to always drop the keep unless it was consumed by keep_back for switching to parse_quotable_robust. Reported by sswander. Thanks!!! Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
@sswander Could you try this? |
|
@kou thanks for the quick fix! Seems to work now. Repro script:running |
Member
Author
|
Thanks. |
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.
GitHub: Fix GH-378
Since CSV#shift re-enters CSV::Parser#parse for each row, parse_quotable_loose left one keep per row in the scanner. Each keep retains a StringScanner and its chunk.
A keep was also leaked when an exception was raised while parsing a row. If the caller rescued it and continued reading from IO, every following keep_drop merged its buffer into the leaked keep.
Use ensure to always drop the keep unless it was consumed by keep_back for switching to parse_quotable_robust.
Reported by sswander. Thanks!!!