| Summary: | ASTERISK-11429: Crash with AMI originates | ||
| Reporter: | Eduard M. (callmewind) | Labels: | |
| Date Opened: | 2008-02-13 02:35:04.000-0600 | Date Closed: | 2011-06-07 14:00:42 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/ManagerInterface |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) AMIConnection.java ( 1) extensions.conf.A ( 2) extensions.conf.B | |
| Description: | This is the continuation of bug ASTERISK-1163698. I returned with more tests and last version 1.4.18 is still crashing. Asterisk is compiled with minimal modules, DEBUG_THREADS, DEBUG_THREAD_LOCALS, DONT_OPTIMIZE and MALLOC_DEBUG. ****** ADDITIONAL INFORMATION ****** The test system is fairly the same: -Machine A: 64 bits Asterisk 1.4.18, and a java application connected to asterisk with Java Asterisk. This application runs a thread which creates random originates. I will attach the code (is simple). -Machine B: 32 bits Asterisk 1.4.18 with a simple dialplan: answer the call, musiconhold for 40 seconds and hangup. The tests runs happy for some time, but sooner or later originates start to fail and finally asterisk of machine A crashes (which is making the originates). | ||
| Comments: | By: Eduard M. (callmewind) 2008-02-13 02:55:18.000-0600 Unafortunately for now I don't have a core file but I will try to reproduce it again with coredump. By: Joshua C. Colp (jcolp) 2008-02-13 09:10:55.000-0600 Crash issues always need to be accompanied by backtraces. By: Eduard M. (callmewind) 2008-02-15 10:02:30.000-0600 I'm sorry, but I've updated the system (gentoo) installing gdb (for backtraces) and now.. is not crashing! Feel free to close the bug, since I think that the problem seems more related to the old gentoo libraries. If it happens again, I will reopen it with the backtraces. By: jmls (jmls) 2008-02-17 12:34:48.000-0600 closing at reporters request | ||