Boost C++ Libraries: Ticket #7755: Thread: deadlock with shared_mutex on Windows

attachment set

Sat, 01 Dec 2012 14:48:33 GMT

attachment → shared_mutex_deadlock.zip

owner, status changed; cc set

viboes — Sat, 01 Dec 2012 22:58:42 GMT

cc viboes added
owner changed from Anthony Williams to viboes
status new → assigned

Hi, since 1.50 there is the possibility to use a common implementation for shared_mutex defining BOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN or BOOST_THREAD_VERSION=3.

Please, could you tell me if this solves the issue?

See #4882.

Mon, 03 Dec 2012 08:05:28 GMT

Defining BOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN solves the issue!!!

status changed; resolution set; milestone deleted

viboes — Mon, 03 Dec 2012 16:08:05 GMT

status assigned → closed
resolution → duplicate
milestone To Be Determined

status changed; milestone set; resolution deleted

viboes — Sat, 19 Jan 2013 10:42:30 GMT

status closed → reopened
resolution duplicate
milestone → To Be Determined

Reopened as BOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN will not be defined by default and as #7906 states there is a lost in performances when this define is defined.

attachment set

viboes — Sun, 03 Mar 2013 21:28:58 GMT

attachment → 7755.patch

anonymous — Sun, 03 Mar 2013 21:30:32 GMT

Replying to Andrey <nikolay@…>:

Please see attached test. Code is very simple. It works when thread3 uses thread3_func_workaround function and test is deadlocked when thread3 uses thread3_func function. From the first view, it seems the problem in the shared_mutex::timed_lock function. Possible it have to signal "semaphores[unlock_sem]" semaphore when state.exclusive_waiting_blocked is changed from true to false. This action will wake up threads which are waiting for shared access.

It seems your analysis were right. Please could you try the attached patch?

milestone changed

viboes — Sun, 03 Mar 2013 21:46:00 GMT

milestone To Be Determined → Boost 1.54.0

status changed; resolution set

viboes — Sat, 23 Mar 2013 02:11:07 GMT

status reopened → closed
resolution → fixed

Committed revision [83525].