[mention removed] for vis. I note this version of curl in 8.12.1 is quite recent and already had some hot fixes. Given how new it is and the latest hotfix within the last few months, I’m now more suspicious of this being an issue in the library. Do we know if there are any other dependencies in 5.6 on this latest version of curl? I assume the engine should work fine against 8.4.0 still.
Edit: well my 100% repro case I hit has gone away with 8.4.0. If no other dependencies exist, we may roll back to 8.4.0 for now to verify it across the team as several people have gotten this at fairly frequent intervals. Possible some relation to this similar sounding cause https://github.com/curl/curl/issues/17139 also found in 8.12.1 though the behavior is different or a prior regression found here https://github.com/curl/curl/issues/15639 (though this one was supposedly fixed before 8.12.0). Could also be downstream of what was fixed in multi: start the loop over when handles are removed by bagder · Pull Request #16588 · curl/curl · GitHub which looks like it could access bogus mem.