[Home]

Summary:ASTERISK-26483: segfault in queued_task_pushed - runs on already destroyed pool
Reporter:Alexei Gradinari (alexei gradinari)Labels:
Date Opened:2016-10-18 09:46:22Date Closed:
Priority:MajorRegression?
Status:Open/NewComponents:Core/General
Versions:13.11.2 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) bt_queued_task_pushed.txt
Description:Got this segfault on PJSIP stress testing.
It seems the function queued_task_pushed runs on an already destroyed pool.
Comments:By: Asterisk Team (asteriskteam) 2016-10-18 09:46:22.936-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) 2016-10-20 20:52:37.606-0500

[~alexei gradinari] thanks! Do you have a debug log to go with the segfault? Were you able to reproduce it more than once?