Hide Forgot
Description of problem: I noticed my cpu running very hot when the backtrace generation was in progress on the retrace server, but this could have started earlier. Top showed this: 15066 amit 20 0 608324 34648 15632 R 99.7 0.4 26:48.23 gnome-abrt I did this: strace -o /tmp/gnome-abrt-strace.txt -p 15066 -f The file is only filled with 15069 restart_syscall(<... resuming interrupted call ...> <unfinished ...> 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 15066 wait4(-1, 0x7fff195712cc, WNOHANG, 0x7fff195712d0) = 0 $ rpm -q gnome-abrt gnome-abrt-0.3.1-1.fc19.x86_64
The 100% cpu usage only dropped after the bug was successfully filed and I closed the window. Just filing of the bug isn't necessary, but closing of the window that pops out which shows progress, etc., is necessary. The main window then got focus, and things returned to normal.
Thank you for the bug report. It is a bug in SIGCHLD signal handler. I believe that this bug is also the root cause of bug #960724.
bug #1008921 is also a consequence of the bug in the signal handler.
Upstream commit 74fadd0f56c0331595eb72ce90ae43ba27f50fb7 fixes this bug.
gnome-abrt-0.3.2-1.fc19,abrt-2.1.8-1.fc19,libreport-2.1.8-1.fc19,satyr-0.10-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/gnome-abrt-0.3.2-1.fc19,abrt-2.1.8-1.fc19,libreport-2.1.8-1.fc19,satyr-0.10-1.fc19
Package gnome-abrt-0.3.2-1.fc19, abrt-2.1.8-1.fc19, libreport-2.1.8-1.fc19, satyr-0.10-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnome-abrt-0.3.2-1.fc19 abrt-2.1.8-1.fc19 libreport-2.1.8-1.fc19 satyr-0.10-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18924/gnome-abrt-0.3.2-1.fc19,abrt-2.1.8-1.fc19,libreport-2.1.8-1.fc19,satyr-0.10-1.fc19 then log in and leave karma (feedback).
gnome-abrt-0.3.2-1.fc19, abrt-2.1.8-1.fc19, libreport-2.1.8-1.fc19, satyr-0.10-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.