Summary: | ASTERISK-25902: res_sorcery_memory_cache: Crash on "sorcery memory cache expire" CLI command | ||
Reporter: | JoshE (n8ideas) | Labels: | |
Date Opened: | 2016-04-07 14:29:49 | Date Closed: | 2016-04-08 09:25:36 |
Priority: | Minor | Regression? | |
Status: | Closed/Complete | Components: | Resources/res_sorcery_memory_cache |
Versions: | 13.7.2 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Attachments: | ( 0) crash-on-sorcery-cache-expire.txt | |
Description: | Observed a crash occurring occasionally on a CLI execution of a sorcery memory cache expire. | ||
Comments: | By: Asterisk Team (asteriskteam) 2016-04-07 14:29:49.630-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: JoshE (n8ideas) 2016-04-07 14:30:57.661-0500 Backtrace attached. By: Joshua C. Colp (jcolp) 2016-04-07 14:47:37.188-0500 This appears to be caused by the code not rejecting "sorcery memory cache expire" without a cache name. A cache name needs to be specified. By: George Joseph (gjoseph) 2016-04-08 09:25:36.260-0500 Fixed with commit 6e70e8ccdb77e772ef877793e88b82daf626db2c |