-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
1
-
2
-
Storage Engines - 2022-09-19
The test, below, failed in test_txn07. According to the core, it triggered an assertion failure in libc_malloc:
Thread 1 (Thread 0x7fb131276740 (LWP 82705)): #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007fb131816859 in __GI_abort () at abort.c:79 #2 0x00007fb1318892da in __malloc_assert (assertion=assertion@entry=0x7fb1319ad8a8 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0x7fb1319a93d6 "malloc.c", line=line@entry=2379, function=function@entry=0x7fb1319ae030 <__PRETTY_FUNCTION__.13066> "sysmalloc") at malloc.c:298 #3 0x00007fb13188b93f in sysmalloc (nb=nb@entry=3000048, av=av@entry=0x7fb1319e0b80 <main_arena>) at malloc.c:2379 #4 0x00007fb13188c793 in _int_malloc (av=av@entry=0x7fb1319e0b80 <main_arena>, bytes=bytes@entry=3000034) at malloc.c:4141 #5 0x00007fb13188e299 in __GI___libc_malloc (bytes=3000034) at malloc.c:3066 #6 0x00007fb13156bbe6 in PyMem_RawMalloc (size=3000034) at ../src/Python-3.9.2/Objects/obmalloc.c:1638 #7 _PyObject_Malloc (ctx=<optimized out>, nbytes=3000034) at ../src/Python-3.9.2/Objects/obmalloc.c:1645 #8 _PyObject_Malloc (nbytes=3000034, ctx=<optimized out>) at ../src/Python-3.9.2/Objects/obmalloc.c:1638 #9 PyObject_Malloc (size=<optimized out>) at ../src/Python-3.9.2/Objects/obmalloc.c:685
gdb also reports that the test is using the tcmalloc shared library:
(gdb) info sharedlibrary From To Syms Read Shared Object Library 0x00007fb131816630 0x00007fb13198b27d Yes (*) /lib/x86_64-linux-gnu/libc.so.6 ... 0x00007fb1304fef90 0x00007fb130748f50 Yes /data/mci/226ebcb573b783c7c5b9a9db3a7f0c6d/wiredtiger/cmake_build/libwiredtiger.so.11.0.1 0x00007fb1302d7630 0x00007fb1302f9ce3 Yes /data/mci/226ebcb573b783c7c5b9a9db3a7f0c6d/wiredtiger/TCMALLOC_LIB/lib/libtcmalloc.so.4
So this is likely another manifestation of the issues fixed in WT-9710.
unit-test-bucket02 on ubuntu2004
Host: i-09748661bd443397e
Project: wiredtiger
Commit: 0ac82ac3
Task Logs:
unit-test-bucket02 task_log
Logs:
Test failure ERROR: test_txn07.test_txn07.test_ops(row.trunc-all.t1r.zlib) (subunit.RemotedTestCase) test_txn07.test_txn07.test_ops(row.trunc-all.t1r.zlib) ---------------------------------------------------------------------- testtools.testresult.real._StringException: lost connection during test 'test_txn07.test_txn07.test_ops(row.trunc-all.t1r.zlib)' ---------------------------------------------------------------------- Ran 875 tests in 268.267s Link: https://evergreen.mongodb.com/task_log_raw/wiredtiger_ubuntu2004_unit_test_bucket02_0ac82ac3fb889ed948dcb23ef77b3cd82d6de935_22_08_29_16_04_24/0?type=T#L3828 Evergreen YAML Script Failure Command failed: shell script encountered problem: exit code 1 Link: https://evergreen.mongodb.com/task_log_raw/wiredtiger_ubuntu2004_unit_test_bucket02_0ac82ac3fb889ed948dcb23ef77b3cd82d6de935_22_08_29_16_04_24/0?type=T#L3838