Actions
Bug #20759
closedmon: valgrind detects a few leaks
Status:
Can't reproduce
Priority:
High
Assignee:
-
Category:
Correctness/Safety
Target version:
-
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Monitor
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
From /a/joshd-2017-07-23_23:56:38-rados:verify-wip-20747-distro-basic-smithi/1435050/remote/smithi036/log/valgrind/mon.a.log.gz
One that is definitely lost is a monitor Session:
<error> <unique>0x24</unique> <tid>1</tid> <kind>Leak_DefinitelyLost</kind> <xwhat> <text>20,553 (360 direct, 20,193 indirect) bytes in 1 blocks are definitely lost in loss record 37 of 39</text> <leakedbytes>20553</leakedbytes> <leakedblocks>1</leakedblocks> </xwhat> <stack> <frame> <ip>0x9E0D203</ip> <obj>/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so</obj> <fn>operator new(unsigned long)</fn> <dir>/builddir/build/BUILD/valgrind-3.11.0/coregrind/m_replacemalloc</dir> <file>vg_replace_malloc.c</file> <line>334</line> </frame> <frame> <ip>0x513658</ip> <obj>/usr/bin/ceph-mon</obj> <fn>new_session</fn> <dir>/usr/src/debug/ceph-12.1.1-411-g3f591d4/src/mon</dir> <file>Session.h</file> <line>145</line> </frame> <frame> <ip>0x513658</ip> <obj>/usr/bin/ceph-mon</obj> <fn>Monitor::_ms_dispatch(Message*)</fn> <dir>/usr/src/debug/ceph-12.1.1-411-g3f591d4/src/mon</dir> <file>Monitor.cc</file> <line>4082</line> </frame> <frame> <ip>0x53C9E2</ip> <obj>/usr/bin/ceph-mon</obj> <fn>Monitor::ms_dispatch(Message*)</fn> <dir>/usr/src/debug/ceph-12.1.1-411-g3f591d4/src/mon</dir> <file>Monitor.h</file> <line>882</line> </frame> <frame> <ip>0x984F21</ip> <obj>/usr/bin/ceph-mon</obj> <fn>ms_deliver_dispatch</fn> <dir>/usr/src/debug/ceph-12.1.1-411-g3f591d4/src/msg</dir> <file>Messenger.h</file> <line>625</line> </frame> <frame> <ip>0x984F21</ip> <obj>/usr/bin/ceph-mon</obj> <fn>DispatchQueue::entry()</fn> <dir>/usr/src/debug/ceph-12.1.1-411-g3f591d4/src/msg</dir> <file>DispatchQueue.cc</file> <line>197</line> </frame> ...
Updated by Greg Farnum over 6 years ago
- Has duplicate Bug #20734: mon: leaks caught by valgrind added
Updated by Kefu Chai over 6 years ago
/kchai-2017-09-21_06:22:45-rados-wip-kefu-testing-2017-09-21-1013-distro-basic-mira/1654844/remote/mira038/log/valgrind/mon.a.log.gz
Updated by Kefu Chai over 6 years ago
/a/kchai-2017-10-21_09:27:38-rados-wip-kefu-testing-2017-10-21-1049-distro-basic-mira/1757648/remote/mira121/log/ceph-mon.a.log.gz
Updated by Josh Durgin over 4 years ago
- Status changed from New to Can't reproduce
Updated by Greg Farnum over 4 years ago
Maybe this was some of the leaked MForwards we weren't marking as no_reply?
Actions