[asterisk-bugs] [JIRA] (ASTERISK-25441) Deadlock in res_sorcery_memory_cache.

[Richard Mudgett (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-25441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Mudgett updated ASTERISK-25441:
---------------------------------------

    Description: A deadlock can happen when a sorcery object is being expired from the memory cache when at the same time another object is being placed into the memory cache.  There are a couple other variations on this theme that could cause the deadlock.  Basically if an object is being expired from the sorcery memory cache at the same time as another thread tries to update the next object expiration timer the deadlock can happen.  (was: A deadlock can happen when a sorcery object is being expired from the memory cache when at the same time another object is being placed into the memory cache.  There are a couple other variations on this theme that could cause the deadlock.  Basically if an object is being expired from the sorcery memory cache at the same time as another thread tries to update the next object expiration timer.)

> Deadlock in res_sorcery_memory_cache.
> -------------------------------------
>
>                 Key: ASTERISK-25441
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25441
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/General
>    Affects Versions: 13.5.0
>            Reporter: Richard Mudgett
>
> A deadlock can happen when a sorcery object is being expired from the memory cache when at the same time another object is being placed into the memory cache.  There are a couple other variations on this theme that could cause the deadlock.  Basically if an object is being expired from the sorcery memory cache at the same time as another thread tries to update the next object expiration timer the deadlock can happen.



--
This message was sent by Atlassian JIRA
(v6.2#6252)