Guest

Preview Tool

Cisco Bug: CSCuq22937 - CM process core under Traffic load due to corrupted memory tracking tree

Last Modified

Feb 03, 2017

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.5(1.98000.194)

Description (partial)

Symptom:
CM process core under Traffic load due to memory corruption.

Conditions:
CUCM Version: 10.5.1.98000-194

backtrace - CUCM
===================================
#0 0x080bd8ba in _S_minimum (__z=0x819df580, __root=@0xb909f14, __leftmost=@0xb909f18, __rightmost=@0xb909f1c) at /view/BLD-cc_mainline_12-raw-d/vob/ccm_tpl/release/include/stlport/stl/_tree.h:94
#1 stlp_std::priv::Rb_global<bool>::_Rebalance_for_erase (_z=0x819df580, __root=@0xb909f14, __leftmost=@0xb909f18, __rightmost=@0xb909f1c) at /view/BLD-cc_mainline_12-raw-d/vob/ccm_tpl/release/include/stlport/stl/_tree.c:157
#2 0x093148fc in erase (memElem=...) at /view/BLD-cc_mainline_12-raw-d/vob/ccm_tpl/release/include/stlport/stl/_tree.h:500
#3 erase (memElem=...) at /view/BLD-cc_mainline_12-raw-d/vob/ccm_tpl/release/include/stlport/stl/_map.h:203
#4 SipMemCache::remove (memElem=...) at ProcessSIPHandler.cpp:368
#5 0x092c622f in mySipFree (p=0x84d72388, fileName=0xaa7eee6 "url_common_parse.cpp", lineNum=2441) at ProcessSIPHandler.cpp:448
#6 0x09c7ffc0 in validate_ip_addr_name (str=0x921df3b2 "10.8.27.176") at url_common_parse.cpp:2441
#7 0x09c815a1 in url_parseSipUrl (url=0x921df3a1 "sip", dup_flag=0 '\000', debug_flag=0 '\000', mp=0x0, strict_parsing=0 '\000') at url_common_parse.cpp:1187
#8 url_parse_generic (url=0x921df3a1 "sip", dup_flag=0 '\000', debug_flag=0 '\000', mp=0x0, strict_parsing=0 '\000') at url_common_parse.cpp:1663
#9 0x09c829ab in url_parse_nameaddr_or_addrspec (input_loc_ptr=0x921df3a0 "", dup_flag=0 '\000', name_addr_only_flag=0 '\000', more_ptr=0xad097f3c, debug_flag=0 '\000') at url_common_parse.cpp:2145
#10 0x09c20901 in sippmh_parse_contact (input_contact=0x830069b1 "<sip:+19570277833@10.8.27.176:57571;transport=tls>;+sip.instance=\"<urn:uuid:00000000-0000-0000-0000-CC17CA0403A5>\";+u.sip!devicename.ccm.cisco.com=\"SEPCC17CA0403A5\";+u.sip!model.ccm.cisco.com=\"503\"") at sip_common_pmh.cpp:1223
#11 0x080866d7 in CMSIPUtility::parseIpPortFromContact (contact=0x830069b1 "<sip:+19570277833@10.8.27.176:57571;transport=tls>;+sip.instance=\"<urn:uuid:00000000-0000-0000-0000-CC17CA0403A5>\";+u.sip!devicename.ccm.cisco.com=\"SEPCC17CA0403A5\";+u.sip!model.ccm.cisco.com=\"503\"", sipAddr=..., contactIpPort=..., contactUserAtIpPort=...) at CMSIPUtility.cpp:3532
#12 0x0942af5d in SIPStationInit::updateDataFromContact (this=0xac4c0a10, sipContainerWrapper=0x8ba10280, contact=0x830069b1 "<sip:+19570277833@10.8.27.176:57571;transport=tls>;+sip.instance=\"<urn:uuid:00000000-0000-0000-0000-CC17CA0403A5>\";+u.sip!devicename.ccm.cisco.com=\"SEPCC17CA0403A5\";+u.sip!model.ccm.cisco.com=\"503\"", contactIpPort=..., contactUserAtIpPort=..., instanceId=..., deviceName=..., sipAddr=..., model=@0xad099634, ciscoPhone=@0xad09963f) at ProcessSIPStationInit.cpp:3550
#13 0x094324d6 in SIPStationInit::wait_SIPRegisterInd (this=0xac4c0a10, s=...) at ProcessSIPStationInit.cpp:981
#14 0x09df138f in SdlProcessBase::inputSignal (this=0xac4c0a10, rSignal=0x828d3910, traceType=SdlSystemLog::SignalRouterThread, highPriority=0, normalPriority=1, lowPriority=0, veryLowPriority=0, lazyPriority=0, dbUpdatePriority=0) at SdlProcessBase.cpp:406
#15 0x09df5d76 in SdlRouter::callProcess (this=0xd929448, _sdlSignal=0x828d3910, _deleteSignal=@0xad09a2ff, _traceType=SdlSystemLog::SignalRouterThread, _hp=0, _np=1, _lp=0, _vlp=0, _lzp=0, _dbp=0) at SdlRouter.cpp:257
#16 0x09df6020 in SdlRouter::scheduler (this=0xd929448) at SdlRouter.cpp:164
#17 0x09df651f in SdlRouter::schedulerInit (sdlRouter=0xd929448) at SdlRouter.cpp:107
#18 0xf6948b39 in start_thread () from /lib/libpthread.so.0
#19 0xf6a49d6e in clone () from /lib/libc.so.6
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.