| Summary: | ASTERISK-25264: Crash in ast_chan_setoption | ||
| Reporter: | JoshE (n8ideas) | Labels: | |
| Date Opened: | 2015-07-17 14:53:48 | Date Closed: | 2020-01-14 11:13:32.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Channels/General |
| Versions: | 11.6.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) ast_chan_setopt_crash.txt | |
| Description: | Crash observed in ast_channel_setoption. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2015-07-17 14:53:50.887-0500 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: JoshE (n8ideas) 2015-07-17 14:54:27.790-0500 Backtrace attached. By: Matt Jordan (mjordan) 2015-07-20 18:40:50.808-0500 Despite the good backtrace, I'm not sure there's enough information here for someone to know why this occurred. A channel not having its technology generally means that there is either a race condition in ConfBridge, or that a masquerade occurred as the result of a transfer. Both of these cases have had innumerable fixes since this version of Asterisk 11. Can you: # Provide instructions for how this problem occurred, or steps to reproduce it on your version of 11? # Does it occur with a more recent version of Asterisk 11? By: JoshE (n8ideas) 2015-07-20 18:44:27.033-0500 This is definitely not the result of a transfer and is a relatively rare condition. Unfortunately, the repro here is difficult as it only occurs under 350-400 channel concurrent load and even then it only pops up around once a week or so, it appears. I can try to run the load testing harness on this to see if I can tease it out. May be also possible to get the version upgraded, but we've tended to stay on the cert6 for this install. By: Rusty Newton (rnewton) 2015-07-31 15:25:05.822-0500 Doesn't appear there is enough here for us to move forward. If you can get a debug log along with the next crash then we can take a look at it again, however without reproduction for this one I'm not sure there is anything we can do yet. By: Asterisk Team (asteriskteam) 2015-08-15 12:00:23.654-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||