| Summary: | ASTERISK-25401: Segmentation-fault crash within pjnath | ||||||
| Reporter: | Stefan Engström (StefanEng86) | Labels: | |||||
| Date Opened: | 2015-09-18 07:50:50 | Date Closed: | 2016-02-10 06:15:09.000-0600 | ||||
| Priority: | Major | Regression? | |||||
| Status: | Closed/Complete | Components: | |||||
| Versions: | 13.5.0 | Frequency of Occurrence | Occasional | ||||
| Related Issues: |
| ||||||
| Environment: | Fedora 20 64-bit, Asterisk 13.5.0, pjprojects 2.4, Chrome SIPml chan_sip client | Attachments: | ( 0) coredump.txt ( 1) gdb.txt | ||||
| Description: | This issue is essentially the same as the closed ASTERISK-24925, but now it has happend when using latest version of pjprojects and asterisk.
Basically a segmentation fault within the pjnath-library (at pj_stun_session_destroy) that happened some time during the dial to a chan_sip webrtc peer which registered from Chrome using SIPml. Possibly related to ASTERISK-25274 ASTERISK-25275 ASTERISK-25317 | ||||||
| Comments: | By: Asterisk Team (asteriskteam) 2015-09-18 07:50:51.879-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: Rusty Newton (rnewton) 2015-09-24 17:39:27.058-0500 Do you have any debug logs to go with the crash? You marked that the crash happens occasionally. Is it frequent enough to get another trace soon with DONT_OPTIMIZE and BETTER_BACKTRACES? Thanks! By: Stefan Engström (StefanEng86) 2015-09-25 10:10:02.500-0500 It happens about once every 2-4 weeks, unfortunately the server in question did not write debug-logs or verbose-logs to file, nor udp-tcpdumps to any persistent storage... I'm not sure how much debugging I'm allowed to activate for that server-machine. Maybe some developer can make an hypothesis what goes wrong, similar to what Dade Brandon tried to do in the old ticket? By: Mark Michelson (mmichelson) 2015-10-01 16:13:24.402-0500 This appears to be a duplicate of ASTERISK-25415, so I am closing this as a duplicate. By: Stefan Engström (StefanEng86) 2015-11-01 11:52:14.946-0600 The issues may very well be duplicates in essence, but I think if you close this you should include Affects version 13.5.0 on the other ticket and possibly link to this issue from the other ticket? Anyways I'm trying to gather more data regarding this issue... It's still very hard to produce the crash reliably! By: Asterisk Team (asteriskteam) 2015-11-01 11:52:15.437-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Abhay Gupta (agupta) 2016-02-10 05:56:56.188-0600 We also get a similar error but in check_cached_response of stun_session.c . Backtrace is attached . and asterisk version was also upgraded to 13.7.2 and issue remains . By: Abhay Gupta (agupta) 2016-02-10 05:58:45.564-0600 backtrace file to show the error . Will use DONT_OPTIMIZE and BETTER_BACTRACES and will submit the backtrace again . By: Joshua C. Colp (jcolp) 2016-02-10 06:14:11.813-0600 [~agupta] Your issue is ASTERISK-25275, not this one | ||||||