[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()

2015-02-04 Thread Chris Halse Rogers
Thank god, we no longer use AsioMainLoop ** Changed in: mir Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to boost1.53 in Ubuntu. https://bugs.launchpad.net/bugs/1243570 Title: helgrind: Lock orde

[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()

2014-09-12 Thread Cemil Azizoglu
Cannot be reproduced any more. ** Changed in: mir Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to boost1.53 in Ubuntu. https://bugs.launchpad.net/bugs/1243570 Title: helgrind: Lock order violated (po

[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()

2014-07-21 Thread Daniel van Vugt
Drop severity. Doesn't qualify for Critical if no one is knowingly affected yet. ** Changed in: mir Importance: Critical => High ** Changed in: boost1.53 (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is su

[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()

2014-04-07 Thread Daniel van Vugt
Just run Mir under helgrind: valgrind --tool=helgrind ... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to boost1.53 in Ubuntu. https://bugs.launchpad.net/bugs/1243570 Title: helgrind: Lock order violated (potential for deadlock)

[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()

2014-04-06 Thread Alberto Aguirre
How do I reproduce this report? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to boost1.53 in Ubuntu. https://bugs.launchpad.net/bugs/1243570 Title: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::

[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()

2014-03-23 Thread Daniel van Vugt
** Changed in: mir Importance: High => Critical ** Changed in: boost1.53 (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to boost1.53 in Ubuntu. https://bugs.launchpad.net/bugs/1243570 Title:

[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()

2014-02-20 Thread Daniel van Vugt
Whichever module is creating the threads is likely to blame. Because that's the module which should be managing locking. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to boost1.53 in Ubuntu. https://bugs.launchpad.net/bugs/1243570 Title

[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()

2014-02-20 Thread kevin gunn
so is this really a bug on mir or aiso ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to boost1.53 in Ubuntu. https://bugs.launchpad.net/bugs/1243570 Title: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_

[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()

2013-12-22 Thread Daniel van Vugt
** Tags added: helgrind -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to boost1.53 in Ubuntu. https://bugs.launchpad.net/bugs/1243570 Title: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run() T