desrt just reminded me (after I reminded him :) that my apparent explanation of the bug doesn't make sense.
We're losing a reference to the GSource and the claimed unsafe callback should actually be safe already (as its caller is designed to hold a ref). Although the workaround that's landed seems to perform well, I'm concerned as to understanding /why/ still... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1401488 Title: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1401488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
