| Summary: | ASTERISK-23037: res_pjsip/distribute: crash when distributing transaction during a mutex unlock in pjsip | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | |
| Date Opened: | 2013-12-19 16:50:28.000-0600 | Date Closed: | 2013-12-30 10:58:09.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_pjsip |
| Versions: | 12.0.0-beta2 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | See the following backtrace in the testsuite for an example:
https://bamboo.asterisk.org/bamboo/artifact/AST-ATTSCD4/C632TE/build-155/Test-Suite-Logs/channels/pjsip/basic_calls/outgoing/off-nominal/bob_incompatible_codecs/backtrace_8037.txt {quote} (04:48:06 PM) mmichelson: mjordan: I think that crash isn't due to calling from incorrect thread. I think we're trying to unlock a mutex that isn't ours. (04:48:18 PM) mmichelson: It may be because the pjsip_transaction got destroyed while we had it locked. (04:49:04 PM) mjordan: well that's just about as disturbing (04:49:13 PM) mmichelson: Yeah, it's definitely not a good thing. {quote} | ||
| Comments: | By: Joshua C. Colp (jcolp) 2013-12-19 17:24:47.330-0600 Until pjproject is updated on Bamboo to the latest version this issue is a red herring. Transaction related locking/reference counting has undergone major changes, specifically to fix problems like this. If it reoccurs after updating then we should further isolate. By: Rusty Newton (rnewton) 2013-12-20 17:10:20.423-0600 I'll open this for now. We can close it after we update and verify. This will serve as a reminder. By: Matt Jordan (mjordan) 2013-12-30 10:58:09.150-0600 This was technically a bug in pjproject and was fixed in the latest release. This bug can be resolved by updating to the latest pjproject in the github repo. | ||