| Summary: | ASTERISK-15891: Segfault error | ||
| Reporter: | Matteo (mpiazzatnetbug) | Labels: | |
| Date Opened: | 2010-03-30 04:24:32 | Date Closed: | 2011-06-07 14:00:24 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) gdb.txt | |
| Description: | I get a segfault error, i don't have any message in the syslog but I foud the core file into the tmp directory. The server has 1100 peers registered on it. The version of asterisk is 1.4.26.3 backtrace dump included ****** ADDITIONAL INFORMATION ****** I'm not sure but this issue could be a replication of 0016446 | ||
| Comments: | By: David Woolley (davidw) 2010-03-30 05:56:08 This isn't a segfault, it is an abort. Specifically it is an abort by the memory allocator. You should at least turn on malloc debugging and see if you can get it to reproduce. Strictly speaking, you should follow the instructions in doc/valgrind.txt, although you may find that the performance hit is unacceptable, if you can't quickly reproduce the problem. You've either had a double close on your music on hold stream, or you have general memory corruption. By: Leif Madsen (lmadsen) 2010-03-31 09:33:55 Also, if this is a duplicate of 16446, then I'd suggest you either test with a newer version of Asterisk, or port the changes from the commit that closed ASTERISK-15315 and incorporate them into your running version of Asterisk. By: Matteo (mpiazzatnetbug) 2010-04-07 07:06:14 Ok I think we can close the ticket for the moment, not easy to reproduce, until now is happened only one time in a month. By: Paul Belanger (pabelanger) 2010-04-07 10:10:46 Feel free to open this again if you run into the problem. | ||