| Summary: | ASTERISK-28039: Null pointer crash for ast_stream_get_type | ||||
| Reporter: | Joshua Elson (joshelson) | Labels: | webrtc | ||
| Date Opened: | 2018-09-05 12:26:29 | Date Closed: | 2018-09-05 12:37:52 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Core/Streams | ||
| Versions: | 15.2.2 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ( 0) core.dfw-media-2018-09-05T10-19-16-0600-brief.txt ( 1) core.dfw-media-2018-09-05T10-19-16-0600-full.txt ( 2) core.dfw-media-2018-09-05T10-19-16-0600-locks.txt ( 3) core.dfw-media-2018-09-05T10-19-16-0600-thread1.txt | |||
| Description: | Been observing this crash multiple times a day on various cluster nodes. Appears to be a null pointer ast_stream_get_type call.
Happens on our heavier use WebRTC nodes. Working to see if we can get a scenario we can repro, but if there's a way to avoid the crash, that'd be lovely. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2018-09-05 12:26:30.288-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: Joshua Elson (joshelson) 2018-09-05 12:27:25.644-0500 Backtraces attached. | ||||