Opened 10 years ago

Last modified 7 years ago

#7807 new Bugs

message_queue do_send and do_receive blocked for interprocess_mutex

Reported by: zyt1013@… Owned by: Ion Gaztañaga
Milestone: To Be Determined Component: interprocess
Version: Boost 1.52.0 Severity: Problem
Keywords: interprocess_mutex Cc:

Description

Sending program A send information to the receiving program B, if the program B quit unexpectedly. Starting the program again B,Program A and B will block in “scoped_lock<interprocess_mutex> lock(p_hdr->m_mutex)”

Change History (5)

comment:1 by viboes, 10 years ago

Component: None → interprocess
Owner: set to Ion Gaztañaga

comment:2 by anonymous, 8 years ago

how can deal with the bugs?

comment:3 by assorted <assortedbeans@…>, 7 years ago

I have same problem. The interprocess_mutex cause deadlock. I use "open_only" flag in client process. If the server is not running, I get a deadlock in timed_receive or try_receive. The message_queue is absolutely unusable.

comment:4 by assorted <assortedbeans@…>, 7 years ago

It helped partly: #define BOOST_INTERPROCESS_ENABLE_TIMEOUT_WHEN_LOCKING

comment:5 by assorted <assortedbeans@…>, 7 years ago

This is a duplicate of #11728 ticket.

Note: See TracTickets for help on using tickets.