Subject: Re: [Boost-bugs] [Boost C++ Libraries] #7720: exception lock_error while intensive locking/unlocking of mutex
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-02-13 07:19:49
#7720: exception lock_error while intensive locking/unlocking of mutex
----------------------------------------+-----------------------------------
Reporter: sergey.stepanov@⦠| Owner: viboes
Type: Bugs | Status: reopened
Milestone: To Be Determined | Component: thread
Version: Boost 1.51.0 | Severity: Regression
Resolution: | Keywords: lock_error
----------------------------------------+-----------------------------------
Changes (by viboes):
* severity: Problem => Regression
Comment:
Replying to [comment:9 Andrey <nikolay@â¦>]:
> Unfortunately, my first project where the problem is reproducible is
really time critical module. It is a reason why the performance issue with
generic implementation has been found in such little time period. I have
made some tests on 1.52 and found that from the performance perspective it
is better for me don't use upgrade_lock at all than use generic
implementation of shared_mutex.
> Now while new release of my program is under development I am waiting
for the fix for this issue. But if it will not be fixed till end of March
I will need to choose:
> - downgrade boost to 1.44 to have fast and bug-free upgrade_lock with
shared_mutex
This is an interesting information. BTW, have you tried 1.45? Do you know
the first version which introduced the regression?
> or
> - rewrite code to don't use upgrade_lock in my projects
I can not ensure you when this will be fixed but the fact this is a
regression would surely help.
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/7720#comment:10> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:12 UTC