StringGetAsync sometimes crash with an ArgumentOutOfRangException #3001
Description
Stack trace:
System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'start')
at StackExchange.Redis.PhysicalConnection.ProcessBuffer(ReadOnlySequence`1& buffer) in /_/src/StackExchange.Redis/PhysicalConnection.cs:line 2135
at StackExchange.Redis.PhysicalConnection.ReadFromPipe() in /_/src/StackExchange.Redis/PhysicalConnection.cs:line 2085
Using version 2.10.1, .NET 8.0 / ARM64 running under Linux as an AWS Lambda
Rare and not reproducible, appear to happen in low memory situations.
Activity
mgravell commentedon Jan 31, 2026
Intriguing. We're tracking a few problems related to low memory problems, and that is a large driver for some ongoing (but incomplete) work to overhaul that part of the core. I'll look at the stack trace location on Monday, thanks.
mgravell commentedon Feb 12, 2026
I've done some digging into this, and while I haven't been able to repro anything specific, there's a lot of crossover here with general low-memory things, that I'm investigating. However, this entire piece of code is due to be ripped out very soon, for a wide range of reasons. I'm going to keep poking it to see if we can find and fix the "old" code, though.
michelemottini commentedon Feb 12, 2026
Thanks Marc
mgravell commentedon Feb 12, 2026
I think what I am going to do is re-prioritize merging the read half of the IO rewrite (already feature complete and heavily tested / optimized), in isolation / anticipation of the later work, to resolve this stability issue once and for all.
mgravell commentedon Feb 16, 2026
relevant context: #3014
mgravell commentedon Mar 2, 2026
Closing as "almost certainly addressed in (incomplete) v3.0"; no specific repro, etc