(05-25-2016, 05:26 AM)jcarpenter Wrote: (05-24-2016, 11:26 PM)Narf Wrote: I don't see how this could happen with 3.0.6 unless there's an actual error while trying to free the lock in question ...
So how do I determine if there is an "actual error while trying to free the lock in question"?
Debugging it on your own?
The error is caused by a delete() call failing for a reason different than RES_NOTFOUND - this is extremely easy to find if you just search for the error message.
I can't help without more info ... You haven't given any details other than an obfuscated error message.
How often does this happen?
Under what conditions exactly?
How do we reproduce it? (not that I have a Memcache instance to work with, but still ...)
Is it reproducible at all?
