-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
The Jenkins stress tests detected memory leaks. For example:
Direct leak of 1060 byte(s) in 53 object(s) allocated from:
#0 0x4a5ce0 in calloc (/mnt/fast/jenkins/workspace/wiredtiger-test-format-stress-sanitizer/build_posix/test/format/t+0x4a5ce0)
#1 0x746fff in __wt_calloc /mnt/fast/jenkins/workspace/wiredtiger-test-format-stress-sanitizer/build_posix/../src/os_common/os_alloc.c:51:11
#2 0xcb25eb in __wt_update_alloc /mnt/fast/jenkins/workspace/wiredtiger-test-format-stress-sanitizer/build_posix/../src/btree/row_modify.c:277:2
#3 0xc716c6 in __wt_col_modify /mnt/fast/jenkins/workspace/wiredtiger-test-format-stress-sanitizer/build_posix/../src/btree/col_modify.c:151:4
#4 0xff5265 in __cursor_col_modify /mnt/fast/jenkins/workspace/wiredtiger-test-format-stress-sanitizer/build_posix/../src/btree/bt_cursor.c:266:10
#5 0xff9997 in __wt_btcur_remove /mnt/fast/jenkins/workspace/wiredtiger-test-format-stress-sanitizer/build_posix/../src/btree/bt_cursor.c:707:10
#6 0xd85a7b in __curfile_remove /mnt/fast/jenkins/workspace/wiredtiger-test-format-stress-sanitizer/build_posix/../src/cursor/cur_file.c:331:2
#7 0x4e5620 in col_remove /mnt/fast/jenkins/workspace/wiredtiger-test-format-stress-sanitizer/build_posix/test/format/../../../test/format/ops.c:1392:9
#8 0x4ddf28 in ops /mnt/fast/jenkins/workspace/wiredtiger-test-format-stress-sanitizer/build_posix/test/format/../../../test/format/ops.c:611:11
#9 0x7f049753adf2 in start_thread (/lib64/libpthread.so.0+0x7df2)
The failure can be seen here http://build.wiredtiger.com:8080/job/wiredtiger-test-format-stress-sanitizer/10560/console
It is likely that this leak was introduced by the recent changes to scrub dirty pages. Doesn't reproduce quickly.