So a few thoughts: * Releasing graphics buffers in case of SIGSEGV seems to be quite dangerous as we are dealing with potentially corrupted memory. I don't think we should take this approach. * It would be nice to have the ability to skip core dumping and instead just produce a threaded stack trace (probably in a gray list maintained by apport). This obviously takes away some information, but it's probably a good tradeoff for the time being. * If we really want to dump, we could investigate into sendfile. I'm not entirely sure that it works with data coming in via stdin, but it's worth a try as we would avoid the kernel -> userspace copy.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278780 Title: apport takes too long to write crash report, appears to lock up phone To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1278780/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
