id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
9055	spin_condition.notify()hangs if communication peer crashes	stepan.seycek@…	Ion Gaztañaga	"When using interprocess_condition for signalling availability of new data in shared memory the call to notify_one() or notify_all() hangs forever if the communication peer terminates ungracefully. This happens because spin_condition.notify() calls m_enter_mut.lock().

A possible solution that we apply in our project is to provide notify methods with a timeout argument and a boolean return value that call m_enter_mut.timed_wait(abs_time). The return value can then be handled accordingly.

"	Bugs	new	To Be Determined	interprocess	Boost 1.54.0	Problem		deadlock