An strace confirms that all three threads interact with libudev. That's bad as libudev is very far away from being thread safe. Only the main thread actually calls recvmsg(), i. e. udev_monitor_receive_device(). But the others do something as well. This isn't expected I figure, as at least the watchdog thread doesn't touch udev at all, and the "t" thread does not talk to libudev but only to umockdev. So *something* leaks into these threads which has no business there.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336671 Title: Intermittent mir_unit_tests.MesaDisplayTest.drm_device_change_event_triggers_handler test failure: device DEVTYPE is sometimes NULL To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1336671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
