| Summary: | ASTERISK-26090: res_http_websocket: Crash when reading message | ||
| Reporter: | Joshua Elson (joshelson) | Labels: | |
| Date Opened: | 2016-06-06 18:30:32 | Date Closed: | 2019-04-17 15:52:04 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_http_websocket |
| Versions: | 11.19.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) ws_safe_read_crash.txt | |
| Description: | Crash found in websockets in ws_safe_read. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-06-06 18:30:32.916-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) 2016-06-06 18:30:52.842-0500 Backtrace attached. By: Rusty Newton (rnewton) 2016-06-14 16:47:33.344-0500 We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Rusty Newton (rnewton) 2016-06-14 16:48:47.009-0500 Thanks for the backtrace, can you in addition provide a debug file showing what happens before the crash (please provide the correlating backtrace as well). Please include the SIP trace inside the debug. The instructions are in the previous comment. By: Asterisk Team (asteriskteam) 2016-06-29 12:00:01.152-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 | ||