[asterisk-bugs] [JIRA] (ASTERISK-21163) crash

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203445#comment-203445 ] 

Matt Jordan commented on ASTERISK-21163:
----------------------------------------

On a slightly different note.

While I appreciate your filing Jira issues - and you do report a lot, which we are thankful for - please go read the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines].

While a backtrace is important and useful, there's a lot of information that could be provided that would be useful, that you should be used to collecting by now. Things like:
* Where did it crash? What were you doing? A summary of 'crash' tells no one who looks at this issue anything about what is going on.
* What are the configuration files on the system? What modules were in use when it crashed?
** If you provided a backtrace, *look* at the backtrace before attaching it. That should give you some hint of where it crashed.
** Hint: on this issue, it's in res_rtp_asterisk. _Already I could now set the component field and provide a more useful summary._
* What version are you running? Is it *really* trunk?
** If you are running an unreleased version of Asterisk, why? You may want to contact developers in #asterisk-dev before filing an issue, as things in trunk are sometimes unstable (hopefully for short periods of time)
** If you are running trunk, was there a version where it did not crash? That can help developers pinpoint the commit that broke trunk.

Reporting issues is always appreciated, however, requiring bug marshals to ask the same questions over, and over, and having to re-update the information in an issue makes them spend time interpreting information that you could have already provided, and reduces the amount of time they have in solving the issue.
                
> crash
> -----
>
>                 Key: ASTERISK-21163
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21163
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: SVN
>         Environment: red hat 1.6.4
> 2.6.32-279.22.1.el6.x86_64
>            Reporter: Private Name
>            Severity: Critical
>         Attachments: bt_full.txt, thread_all_bt.txt
>
>
> Asterisk 11 crashes with very little load every 10 to 30 minutes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira