Description
See <http://mjc.homeunix.org:8180/job/wiredtiger-clang-sanitizer/845/changes>
The output from smoke.sh.log in bench/wtperf says:
=================================================================
|
==7471==ERROR: LeakSanitizer: detected memory leaks
|
|
Direct leak of 29920 byte(s) in 34 object(s) allocated from:
|
#0 0x476381 in calloc (/fast/jenkins/jenkins/workspace/wiredtiger-clang-sanit
|
izer/build_posix/bench/wtperf/wtperf+0x476381)
|
WT-1 0x4e9fbd in __wt_calloc /fast/jenkins/jenkins/workspace/wiredtiger-clang-s
|
anitizer/build_posix/../src/os_posix/os_alloc.c:38
|
|
Direct leak of 3536 byte(s) in 34 object(s) allocated from:
|
#0 0x476381 in calloc (/fast/jenkins/jenkins/workspace/wiredtiger-clang-sanit
|
izer/build_posix/bench/wtperf/wtperf+0x476381)
|
WT-1 0x4e9fbd in __wt_calloc /fast/jenkins/jenkins/workspace/wiredtiger-clang-s
|
anitizer/build_posix/../src/os_posix/os_alloc.c:38
|
WT-2 0x512ded in __wt_open_session /fast/jenkins/jenkins/workspace/wiredtiger-c
|
lang-sanitizer/build_posix/../src/session/session_api.c:933
|
|
SUMMARY: AddressSanitizer: 33456 byte(s) leaked in 68 allocation(s).
|
This is almost certainly from my lsm thread changes. I'll look into it tomorrow.