Updates:
Status: Fixed
Comment #6 on issue 294 by dorma...@rydia.net: segfault under low memory
conditions
http://code.google.com/p/memcached/issues/detail?id=294
Guess I never answered the guy... people should google before asking :)
I've merged trond's thing which at least gives
Comment #3 on issue 294 by bryan.ch...@gmail.com: segfault under low memory
conditions
http://code.google.com/p/memcached/issues/detail?id=294
This seems to happen to me at least once day. The only clue I have comes
from dmesg (entries are from the last 3 days):
32301.972297]
Comment #4 on issue 294 by dorma...@rydia.net: segfault under low memory
conditions
http://code.google.com/p/memcached/issues/detail?id=294
We need a backtrace for those crashes. There's no way to tell what happened
from just the segfault.
Can you please get a backtrace?
Updates:
Status: Started
Comment #1 on issue 294 by trond.no...@gmail.com: segfault under low memory
conditions
http://code.google.com/p/memcached/issues/detail?id=294
We don't check if cq_new returns NULL or not.. I've added a test for that
and submitted a pull request
Updates:
Owner: trond.no...@gmail.com
Comment #2 on issue 294 by trond.no...@gmail.com: segfault under low memory
conditions
http://code.google.com/p/memcached/issues/detail?id=294
(No comment was entered for this change.)
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 294 by ke...@tellapart.com: segfault under low memory conditions
http://code.google.com/p/memcached/issues/detail?id=294
Under certain low memory conditions, memcached can segfault. I cannot
reproduce this manually, but
