Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.8.2
-
None
Description
I've encountered an intermittent segfault while running the couchbase-python-client unit tests. Initially I thought it was related to private changes I made to the client code, but it also appears to happen running from the couchbase-python-client master. It's hard to tell if it's a specific piece of functionality that is crashing, but it appears to happen pretty often on the 'bad_host' test. This is the place it segfaults:
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x10)
|
frame #0: 0x0000000105867799 libcouchbase.2.dylib`lcb::clconfig::Confmon::do_next_provider(this=0x0000000102500690) at confmon.cc:248
|
245 for (ProviderList::const_iterator ii = active_providers.begin();
|
246 ii != active_providers.end(); ++ii) {
|
247 ConfigInfo *info;
|
-> 248 Provider* cached_provider = *ii;
|
249 info = cached_provider->get_cached();
|
250 if (!info) {
|
251 continue;
|
Target 0: (python2.7) stopped.
|
Have only just spotted this, so not sure how easy it is to reproduce outside this test.
Attachments
For Gerrit Dashboard: CCBC-866 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
94732,3 | CCBC-866: check cached provider isn't NULL | master | libcouchbase | Status: MERGED | +2 | +1 |
109842,5 | CCBC-866: track invalidated active_provider_list using unique ID (3.0.0-alpha3) | master | libcouchbase | Status: MERGED | +2 | +1 |
109845,18 | PYCBC-546: Pull in fix in LCB for test_bad_host segfault | master | couchbase-python-client | Status: MERGED | +2 | +1 |
109850,2 | CCBC-866: track invalidated list using unique ID (2.10.3) | master | libcouchbase | Status: ABANDONED | -2 | +1 |
109907,7 | CCBC-866: track invalidated list using unique ID (2.10.3) | release-2.10 | libcouchbase | Status: MERGED | +2 | +1 |