(05-25-2016, 01:53 PM)Narf Wrote: Best thing I could look at is the call details (method names & params, similar to a stack trace) for all CI_Session_redis_driver methods, in the order that they appear, for the request that triggers the issue (and ideally for the one preceeding it too). I'm afraid this is hard to obtain without monkey-patching the class to log that info.
I could also look at your code, the pieces that do session-related stuff anyway, but I highly doubt seeing anything related to this particular issue - that's a waste of time.
But in any case, that would (hopefully) give me just enough to make an educated guess ... I sense that you're relying too much on my directions, for something that you are more well-equipped for in this instance - I can't reproduce the issue, I don't even have Redis or Memcached, I can do literally nothing but guess. It's not that you're completely on your own, but rather you don't really need my help as much as you think you do.
Thanks, I've added a ton of logging to the Redis library to see if I can make sense of what's happening. Annoyingly it's hard to replicate and I haven't found a specific set of steps to reproduce the error reliably. When I can narrow it down I'll post any info I find.
What Redis extension did you develop with? phpredis?
