[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()
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 order violated (potential for deadlock) in boost::asio::io_service::run() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1243570/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()
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 (potential for deadlock) in boost::asio::io_service::run() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1243570/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()
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 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() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1243570/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()
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) in boost::asio::io_service::run() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1243570/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()
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::run() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1243570/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()
** 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: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1243570/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()
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: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1243570/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()
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_service::run() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1243570/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243570] Re: helgrind: Lock order violated (potential for deadlock) in boost::asio::io_service::run()
** 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() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1243570/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
