Closed (fixed)
Project:
Memcache API and Integration
Version:
8.x-2.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Feb 2016 at 15:39 UTC
Updated:
27 Sep 2016 at 09:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
h3rj4n commentedAnd the patch.
Comment #3
damiankloip commentedHmm, sorry. I can't replicate this. You just enabled the module and that was it? If memcache doesn't have the key it should not return an item at all AFAIK, not an empty item with FALSE in. Can you post a debug of what is in $results before the error?
Comment #4
damiankloip commentedComment #5
vurt commentedI got this error too, and the patch fixes it.
It happens for example when I run "drush cr". I have devel and webprofiler modules (among others) enabled - maybe you can reproduce it with this information.
I have attached the error message with stack trace.
Comment #6
jcnventuraIndeed, this patch also fixed my 'drush cr'.
@damiankloip, in reply to your question in #3, the value of $result is NULL in those cases where a Fatal error is triggered, requiring this patch to not do so.
The second part of this patch where the $cache->tags are set to an empty array do not seem to be needed once the "is_object($result)" condition is added. If you call $this->valid with $result = NULL, then setting the tags to an empty array does avoid a warning, but I don't think it's necessary.
Comment #7
jcnventuraSetting to needs work, since as I said in #6, the second half of the patch may not be necessary.
Comment #8
jcnventuraRelated issue solved the problem almost the same way as the first half of the patch. But the is_object test is probably better.
Comment #9
jcnventuraComment #10
damiankloip commentedSorry, I am still not seeing this as being the correct fix. I think if we are getting completely empty items, they should be filtered out. Are you using Memcache or Memcached ?
Comment #11
aspilicious commentedI'm experiencing the same issue, using memcached.
Comment #12
vurt commentedWithout the patch I cannot use the module. I am using memcached too.
Comment #13
googletorp commentedCould we please get the patch committed, module is 100% useless in current release which this patch fixes. Rolling out a new release after patch has been applied would help a lot of people.
Comment #14
jphautin commentedHello,
Just create a fresh installation with drupal 8.1.8. This is the only (and first) module installed (with memcached) in version 8.x-2.0-alpha1.
Same issue on line 105 of MemcacheBackend.php.
Using same solution to make module usable by applying same modification on line 105 (is 102 in the patch for dev version).
regards,
Comment #15
damiankloip commentedCan you test this patch please.
Comment #16
vurt commentedThis patch also works fine for me, thanks!
Comment #17
tim_djpatch #15 works perfect for me
Comment #18
googletorp commentedComment #19
cameron tod commentedMemcache caused instant WSODs for me without this patch. I applied it and memcache now appears to work perfectly. +1
Comment #20
damiankloip commentedThank you all, going to merge this now and just create a new release.
It seems to only be Memcached that people see issues.
Comment #22
damiankloip commented