[Home]

Summary:ASTERISK-27626: PJSIP asserts in "tsx_on_state_completed_uas"
Reporter:snuffy (snuffy)Labels:pjsip
Date Opened:2018-01-25 18:57:17.000-0600Date Closed:
Priority:MinorRegression?No
Status:Open/NewComponents:pjproject/pjsip
Versions:GIT Frequency of
Occurrence		Frequent
Related
Issues:
Environment:debian 9 compiled with 'dev-mode' 'don't optimise' 'better backtraces'Attachments:( 0) core.asterisk-1080-1516867033-brief.txt
( 1) core.asterisk-1080-1516867033-full.txt
( 2) core.asterisk-1080-1516867033-locks.txt
( 3) core.asterisk-1080-1516867033-thread1.txt
( 4) core.asterisk-23668-1516925353-brief.txt
( 5) core.asterisk-23668-1516925353-full.txt
( 6) core.asterisk-23668-1516925353-locks.txt
( 7) core.asterisk-23668-1516925353-thread1.txt
Description:Getting a few crashes with this same set of tracing:

#0  0x00007f7b989d0067 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007f7b989d1448 in __GI_abort () at abort.c:89
#2  0x00007f7b989c9266 in __assert_fail_base (fmt=0x7f7b98b01f18 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
   assertion=assertion@entry=0x7f7b9b4d7650 "event->type == PJSIP_EVENT_TX_MSG && event->body.tx_msg.tdata == tsx->last_tx",
   file=file@entry=0x7f7b9b4d70b8 "../src/pjsip/sip_transaction.c", line=line@entry=3262,
   function=function@entry=0x7f7b9b4d7b50 <__PRETTY_FUNCTION__.7428> "tsx_on_state_completed_uas") at assert.c:92
#3  0x00007f7b989c9312 in __GI___assert_fail (
   assertion=assertion@entry=0x7f7b9b4d7650 "event->type == PJSIP_EVENT_TX_MSG && event->body.tx_msg.tdata == tsx->last_tx",
   file=file@entry=0x7f7b9b4d70b8 "../src/pjsip/sip_transaction.c", line=line@entry=3262,
   function=function@entry=0x7f7b9b4d7b50 <__PRETTY_FUNCTION__.7428> "tsx_on_state_completed_uas") at assert.c:101


#0  0x00007fcc36d6e067 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007fcc36d6f448 in __GI_abort () at abort.c:89
#2  0x00007fcc36d67266 in __assert_fail_base (fmt=0x7fcc36e9ff18 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
   assertion=assertion@entry=0x7fcc39875650 "event->type == PJSIP_EVENT_TX_MSG && event->body.tx_msg.tdata == tsx->last_tx",
   file=file@entry=0x7fcc398750b8 "../src/pjsip/sip_transaction.c", line=line@entry=3262,
   function=function@entry=0x7fcc39875b50 <__PRETTY_FUNCTION__.7428> "tsx_on_state_completed_uas") at assert.c:92
#3  0x00007fcc36d67312 in __GI___assert_fail (
   assertion=assertion@entry=0x7fcc39875650 "event->type == PJSIP_EVENT_TX_MSG && event->body.tx_msg.tdata == tsx->last_tx",
   file=file@entry=0x7fcc398750b8 "../src/pjsip/sip_transaction.c", line=line@entry=3262,
   function=function@entry=0x7fcc39875b50 <__PRETTY_FUNCTION__.7428> "tsx_on_state_completed_uas") at assert.c:101
Comments:By: Asterisk Team (asteriskteam) 2018-01-25 18:57:18.964-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: snuffy (snuffy) 2018-01-25 19:00:29.458-0600

Backtraces from asterisk
By: snuffy (snuffy) 2018-01-25 19:11:47.879-0600

backtraces etc
By: Corey Farrell (coreyfarrell) 2018-01-25 19:20:54.561-0600

I'm acknowledging this.  I've changed the title and reduced severity as this is only an issue in dev-mode.