I'm not an Ubuntu developer, but I ran across this issue while investigating another. To me this smells like a kernel/hardware issue where the killall5 process is a victim during a call to malloc(). If you are able to reproduce, and can capture the output of 'dmesg' on the system after this error has occurred and before rebooting, it might be helpful to diagnose this bug.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/607013 Title: killall5 assert failure: *** glibc detected *** pidof: double free or corruption (out): 0x09a1cec8 *** -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
