Actions
Bug #18735
closedrgw tests fail on centos "saw valgrind issues" v0.94.10
Status:
Resolved
Priority:
Urgent
Assignee:
-
Target version:
-
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
rgw
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Runs:
http://pulpito.ceph.com/teuthology-2017-01-28_16:28:47-rgw-hammer---basic-smithi/
http://pulpito.ceph.com/teuthology-2017-01-28_22:35:40-rgw-hammer---basic-vps/
yuriw@teuthology ~ [16:38:16]> zgrep Leak_StillReachable /a/teuthology-2017-01-28_16:28:47-rgw-hammer---basic-smithi/759429/remote/smithi137/log/valgrind/mon.a* -b20 -a20 937- <arg>-f</arg> 955- <arg>-i</arg> 973- <arg>a</arg> 990- </argv> 1000-</args> 1008- 1009-<status> 1018- <state>RUNNING</state> 1043- <time>00:00:00:00.053 </time> 1075-</status> 1085- 1086- 1087-<status> 1096- <state>FINISHED</state> 1122- <time>00:00:18:01.536 </time> 1154-</status> 1164- 1165-<error> 1173- <unique>0xc</unique> 1196- <tid>1</tid> 1211: <kind>Leak_StillReachable</kind> 1246- <xwhat> 1256- <text>8 bytes in 1 blocks are still reachable in loss record 13 of 82</text> 1337- <leakedbytes>8</leakedbytes> 1370- <leakedblocks>1</leakedblocks> 1405- </xwhat> 1416- <stack> 1426- <frame> 1438- <ip>0x4C28203</ip> 1463- <obj>/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so</obj> 1534- <fn>operator new(unsigned long)</fn> 1577- <dir>/builddir/build/BUILD/valgrind-3.11.0/coregrind/m_replacemalloc</dir> 1658- <file>vg_replace_malloc.c</file> 1697- <line>334</line> 1720- </frame> 1733- <frame> 1745- <ip>0x4E49960</ip> 1770- <obj>/usr/lib64/libtcmalloc.so.4.2.6</obj> 1819- </frame> 1832- <frame> 1844- <ip>0x400F1E2</ip> -- 2046- <ip>0x3</ip> 2065- </frame> 2078- <frame> 2090- <ip>0xFFF000C9A</ip> 2117- </frame> 2130- <frame> 2142- <ip>0xFFF000CA3</ip> 2169- </frame> 2182- <frame> 2194- <ip>0xFFF000CA6</ip> 2221- </frame> 2234- <frame> 2246- <ip>0xFFF000CA9</ip> 2273- </frame> 2286- </stack> 2297-</error> 2306- 2307-<error> 2315- <unique>0xd</unique> 2338- <tid>1</tid> 2353: <kind>Leak_StillReachable</kind> 2388- <xwhat> 2398- <text>8 bytes in 1 blocks are still reachable in loss record 14 of 82</text> 2479- <leakedbytes>8</leakedbytes> 2512- <leakedblocks>1</leakedblocks> 2547- </xwhat> 2558- <stack> 2568- <frame> 2580- <ip>0x4C28203</ip> 2605- <obj>/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so</obj> 2676- <fn>operator new(unsigned long)</fn> 2719- <dir>/builddir/build/BUILD/valgrind-3.11.0/coregrind/m_replacemalloc</dir> 2800- <file>vg_replace_malloc.c</file> 2839- <line>334</line> 2862- </frame> 2875- <frame> 2887- <ip>0x4E5DD4D</ip> 2912- <obj>/usr/lib64/libtcmalloc.so.4.2.6</obj> 2961- </frame> 2974- <frame> 2986- <ip>0x4E499FF</ip> -- 3287- <ip>0x3</ip> 3306- </frame> 3319- <frame> 3331- <ip>0xFFF000C9A</ip> 3358- </frame> 3371- <frame> 3383- <ip>0xFFF000CA3</ip> 3410- </frame> 3423- <frame> 3435- <ip>0xFFF000CA6</ip> 3462- </frame> 3475- <frame> 3487- <ip>0xFFF000CA9</ip> 3514- </frame> 3527- </stack> 3538-</error> 3547- 3548-<error> 3556- <unique>0x1e</unique> 3580- <tid>1</tid> 3595: <kind>Leak_StillReachable</kind> 3630- <xwhat> 3640- <text>30 bytes in 1 blocks are still reachable in loss record 31 of 82</text> 3722- <leakedbytes>30</leakedbytes> 3756- <leakedblocks>1</leakedblocks> 3791- </xwhat> 3802- <stack> 3812- <frame> 3824- <ip>0x4C28203</ip> 3849- <obj>/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so</obj> 3920- <fn>operator new(unsigned long)</fn> 3963- <dir>/builddir/build/BUILD/valgrind-3.11.0/coregrind/m_replacemalloc</dir> 4044- <file>vg_replace_malloc.c</file> 4083- <line>334</line> 4106- </frame> 4119- <frame> 4131- <ip>0x6B8FC78</ip> 4156- <obj>/usr/lib64/libstdc++.so.6.0.19</obj> 4204- <fn>std::string::_Rep::_S_create(unsigned long, unsigned long, std::allocator<char> const&)</fn> 4317- </frame> 4330- <frame>
Updated by Nathan Cutler about 7 years ago
AFAIK the presence of tcmalloc in the stack trace means the valgrind error can be ignored as a false positive.
Updated by Orit Wasserman almost 7 years ago
- Status changed from New to Resolved
Actions