Mir

helgrind: Lock order violated in mir::client::ConnectionSurfaceMap::erase(int)

Bug #1243584 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Medium
Alan Griffiths
mir (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

helgrind: Lock order violated in mir::client::ConnectionSurfaceMap::erase(int)

==21606== ----------------------------------------------------------------
==21606==
==21606== Thread #2: lock order "0x9258A30 before 0x9258338" violated
==21606==
==21606== Observed (incorrect) order is: acquisition of lock at 0x9258338
==21606== (stack unavailable)
==21606==
==21606== followed by a later acquisition of lock at 0x9258A30
==21606== at 0x4C2FC35: pthread_mutex_lock (in /usr/lib/valgrind/vgpreload_helgrind-amd64-linux.so)
==21606== by 0x4F9EB21: __gthread_mutex_lock(pthread_mutex_t*) (gthr-default.h:748)
==21606== by 0x4F9F171: std::mutex::lock() (mutex:134)
==21606== by 0x4FAFE86: std::unique_lock<std::mutex>::lock() (mutex:511)
==21606== by 0x4FAFC30: std::unique_lock<std::mutex>::unique_lock(std::mutex&) (mutex:443)
==21606== by 0x4FC18E0: mir::client::ConnectionSurfaceMap::erase(int) (surface_map.cpp:58)
==21606== by 0x4FAA2CB: MirConnection::released(MirConnection::SurfaceRelease) (mir_connection.cpp:159)
==21606== by 0x4FAF3E6: google::protobuf::internal::MethodClosure1<MirConnection, MirConnection::SurfaceRelease>::Run() (common.h:921)
==21606== by 0x4FD0EBD: mir::client::rpc::MirSocketRpcChannel::receive_file_descriptors(google::protobuf::Message*, google::protobuf::Closure*) (mir_socket_rpc_channel.cpp:211)
==21606== by 0x4FE7136: google::protobuf::internal::MethodClosure2<mir::client::rpc::MirSocketRpcChannel, google::protobuf::Message*, google::protobuf::Closure*>::Run() (common.h:969)
==21606== by 0x4FE7D08: mir::client::rpc::detail::PendingCallCache::complete_response(mir::protobuf::wire::Result&) (mir_basic_rpc_channel.cpp:69)
==21606== by 0x4FD195B: mir::client::rpc::MirSocketRpcChannel::read_message() (mir_socket_rpc_channel.cpp:372)
==21606==
==21606== ----------------------------------------------------------------

Tags: helgrind

Related branches

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

It would be useful to know which program generated the above trace

Changed in mir:
assignee: nobody → Alan Griffiths (alan-griffiths)
Changed in mir:
status: New → In Progress
Changed in mir:
milestone: none → 0.1.4
tags: added: helgrind
Changed in mir:
importance: Undecided → Medium
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir/devel at revision 1316, scheduled for release in mir, milestone Unknown

Changed in mir:
status: In Progress → Fix Committed
Changed in mir:
status: Fix Committed → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

mir (0.1.4+14.04.20140204-0ubuntu1) trusty; urgency=medium

Changed in mir (Ubuntu):
importance: Undecided → Medium
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.