Description of problem: The code in write_dump on abrt_exception_handler.py opens a sockets and writes to it without setting a timeout. If for some reason no one picks up the data the program might hang forever while crashing. Please set a timeout as the process's resources are still being held while it is stuck and cause problems when trying to recover from crashes. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
care to beta-test? http://koji.fedoraproject.org/koji/taskinfo?taskID=3979664 And also would be great if someone can send us strace output of that stalled app.
abrt-2.0.7-3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/abrt-2.0.7-3.fc16
Package abrt-2.0.7-3.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.7-3.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-6193/abrt-2.0.7-3.fc16 then log in and leave karma (feedback).
abrt-2.0.10-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abrt-2.0.10-3.fc17
abrt-2.0.10-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
abrt-2.0.7-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
I believe the root cause of the other side not responding is in https://bugzilla.redhat.com/show_bug.cgi?id=873815.