| Summary: | ASTERISK-15923: Segfault with too many IMAP voicemails | ||
| Reporter: | Noah Miller (noahisaac) | Labels: | |
| Date Opened: | 2010-04-07 15:34:48 | Date Closed: | 2011-06-07 14:00:54 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_voicemail/IMAP |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) gdb.txt | |
| Description: | Asterisk segfaults when too many IMAP voicemails are in a single mailbox/folder. On my particular test system, the number is about 260. ****** STEPS TO REPRODUCE ****** Any access to a mailbox that contains too many messages. ****** ADDITIONAL INFORMATION ****** Tested versions that are affected: Asterisk 1.6.1.6 - 1.6.1.18, Asterisk 1.6.2.6 IMAP Servers Tested: Dovecot 1.0.7 and 1.2.10, Courier (not sure of courier version) MTA: Postfix using Maildir storage | ||
| Comments: | By: Paul Belanger (pabelanger) 2010-04-07 15:46:55 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description didn\'t include enough information. You may find it helpful to read \"Asterisk Issue Guidelines\" http://www.asterisk.org/developers/bug-guidelines. [^] We\'d be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). This likely includes output from the console with debug level logging, a SIP trace (if this is SIP related), and configuration information such as dialplan (e.g. extensions.conf) and channel configuration (e.g. sip.conf). We also require a backtrace from the core file produced after the crash. Please see the doc/backtrace.txt file in your Asterisk source directory. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then: make install after enabling, reproduce the crash, and then execute the instructions in doc/backtrace.txt. When complete, attach that file to this issue report. Thanks! By: Noah Miller (noahisaac) 2010-04-13 13:09:52 Finally got around to making a backtrace. bt, bt full, and thread apply all bt By: Tilghman Lesher (tilghman) 2010-08-04 12:07:45 Your backtrace appears to contain memory corruption and we require valgrind output in order to move this issue forward. Please see the doc/valgrind.txt file in your Asterisk source directory for more information about how to produce debugging information. Thanks! By: Paul Belanger (pabelanger) 2010-08-18 07:57:56 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines | ||