After Restarting Process getting stuck while using Interprocess shared memory API

[anonymous]

WE are interprocess shared memory for caching data across restart. Recently while testing it is found that thread are hanged while acquiring process shared mutex which is member named m_header in boost::interprocess::segment_manager. I think when process was restarted the m_header recursive mutex was in locked state, so when process restarted it finds the mutex in locked state.
I need a mechanism to detect sanity of such locks to detect whether mutex is in stale state.

Regards Aditya Kumar Sinha

[aditya.sinha@…]

WE are interprocess shared memory for caching data across restart. Recently while testing it is found that thread are hanged while acquiring process shared mutex which is member named m_header in boost::interprocess::segment_manager. I think when process was restarted the m_header recursive mutex was in locked state, so when process restarted it finds the mutex in locked state. I need a mechanism to detect sanity of such locks to detect whether mutex is in stale state.

Regards
Aditya Kumar Sinha

[Ion Gaztañaga]

Sorry but robust mutexes are not supported in Interprocess. Maybe in the future.