• Travis Cross's avatar
    Check for null hash on increment of mod_hash limit · 622e0e1a
    Travis Cross 提交于
    When we specifically release all limits on a channel we destroy the
    hash table stored in the "limit_hash" private channel data but we
    don't destroy the private data as it will be reclaimed as part of the
    session.  If limit increment is called after the limit release we can
    reuse that channel private, but we need to check whether the hash
    table is null first.  Fortunately this makes the code look better
    anyway.
    
    FS-6775 #resolve
    FS-6783 #resolve
    622e0e1a
名称
最后提交
最后更新
..
applications 正在载入提交数据...
asr_tts 正在载入提交数据...
codecs 正在载入提交数据...
dialplans 正在载入提交数据...
directories/mod_ldap 正在载入提交数据...
endpoints 正在载入提交数据...
event_handlers 正在载入提交数据...
formats 正在载入提交数据...
languages 正在载入提交数据...
legacy/languages/mod_lua 正在载入提交数据...
loggers 正在载入提交数据...
say 正在载入提交数据...
sdk/autotools 正在载入提交数据...
timers 正在载入提交数据...
xml_int 正在载入提交数据...
.gitignore 正在载入提交数据...
Makefile.am 正在载入提交数据...