https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192889
--- Comment #12 from Arne Claus <arne.cl...@trivago.com> --- We're now running tests with the following configuration FreeBSD 10.1-RELEASE (GENERIC) #0 r274401 memcached 1.4.22 libevent 2.0.21-stable As of now everything works fine, so the situation has at least improved. As I did not see any directly related changes on the FreeBSD changelog (the TCP fixes seem not be relevant for this case) my current assumption is that changes in memcached 1.4.22 fixed the issue. I did not test 1.4.22 on FreeBSD 10.0 though. As the bug shows signs of a race condition especially the threading fixes in memcached 1.4.22 are good candidates for having fixed the issue: https://code.google.com/p/memcached/wiki/ReleaseNotes1422#Memcached_1.4.22_Release_Notes -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
