Description of problem: After logging in, a series of gdb processes spawned by abrtd will consistently consume 100% of CPU. After a while (15 minutes or more) the gdb processes will go away. Here is the output from ps -ejH showing the process tree: 554 554 554 ? 00:00:00 abrtd 1558 554 554 ? 00:00:00 abrt-handle-eve 1622 1622 554 ? 00:00:00 sh 1626 1622 554 ? 00:00:21 abrt-action-gen 2268 2268 2268 ? 00:00:11 gdb Here is the corresponding top output: top - 18:10:37 up 21 min, 2 users, load average: 1.08, 1.39, 1.19 Tasks: 177 total, 3 running, 174 sleeping, 0 stopped, 0 zombie %Cpu(s): 32.7 us, 1.5 sy, 0.0 ni, 65.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 5249864 total, 1148684 used, 4101180 free, 38884 buffers KiB Swap: 4063228 total, 0 used, 4063228 free, 381660 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2268 root 20 0 207m 125m 11m R 99.0 2.4 0:08.46 gdb 1645 smcc 20 0 2040m 227m 34m S 34.1 4.4 7:40.27 gnome-shell 711 root 20 0 206m 59m 8820 S 2.5 1.2 0:44.05 Xorg 1626 root 20 0 154m 3864 1020 S 1.7 0.1 0:21.80 abrt-action-gen 1547 smcc 20 0 200m 1536 1016 S 0.8 0.0 0:07.20 VBoxClient 1 root 20 0 50640 6916 3352 S 0.0 0.1 0:02.91 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 0:00.13 ksoftirqd/0 5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H 7 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/u:0H 8 root rt 0 0 0 0 S 0.0 0.0 0:00.02 migration/0 9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh 10 root 20 0 0 0 0 S 0.0 0.0 0:01.99 rcu_sched 11 root rt 0 0 0 0 S 0.0 0.0 0:00.04 watchdog/0 Version-Release number of selected component (if applicable): abrt-2.0.20-1.fc18 (64-bit) How reproducible: This happens consistently just after I log in. No extra steps are needed. Additional info: I am running Fedora 18 as a guest inside a VirtualBox 4.6.2 r82870 VM running on a Windows 7 host.
I'm still seeing this issue after several large batches of software updates, including 2 kernel updates. I was able to generate some more-detailed information using ps -eHf --cols=1024, which I will attach. The offending process, pid 2561, was run with this command line: gdb -batch -ex set debug-file-directory / -ex file /usr/bin/gnome-shell -ex core-file ./coredump -ex thread apply all backtrace 256 full -ex info sharedlib -ex print (char*)__abort_msg -ex print (char*)__glib_assert_msg -ex info registers -ex disassemble It looks like something is going wrong while examining a core file from gnome-shell.
Created attachment 700901 [details] Output of ps -eHf, showing process tree.
There is a 4 minutes timeout which as it seems is not working
+1 from me. I use the latest VirtualBOX with Win7 - inside is running fedora core 18 - gdb eats all my virtual resources. I have the same issue.
This issue happens on my VirtualBox as well. As a workarroud I have to stop the abrtd service and start it again, then the high CPU will be stopped.
The latest updates from yum seems to have fixed this for me. Running Fedora core 18 in Virtual box as well. Here's the output from "yum history info" on my last updates transaction. Loaded plugins: langpacks, presto, refresh-packagekit Transaction ID : 121 Begin time : Thu Mar 21 11:02:51 2013 Begin rpmdb : 1584:5f1619abc94b0f1f74aad8c77ef1e025870a628f End time : 11:07:35 2013 (284 seconds) End rpmdb : 1584:49b38578bcbb199f492fe27a87966a920a382d6b User : Jean-Francois Beaulac <jbeaulac> Return-Code : Success Command Line : update Transaction performed with: Installed rpm-4.10.3.1-1.fc18.x86_64 @updates Installed yum-3.4.3-51.fc18.noarch @updates Installed yum-metadata-parser-1.1.4-7.fc18.x86_64 @fedora Installed yum-presto-0.9.0-1.fc18.noarch @fedora Packages Altered: Updated empathy-3.6.3-2.fc18.x86_64 @updates Update 3.6.4-2.fc18.x86_64 @updates Updated fedora-release-notes-18.0.0-3.fc18.noarch @fedora Update 18.0.0-5.fc18.noarch @updates Updated gnome-online-accounts-3.6.2-2.fc18.x86_64 @updates Update 3.6.3-1.fc18.x86_64 @updates Updated gutenprint-5.2.9-2.fc18.x86_64 @fedora Update 5.2.9-7.fc18.x86_64 @updates Updated gutenprint-cups-5.2.9-2.fc18.x86_64 @fedora Update 5.2.9-7.fc18.x86_64 @updates Erase kernel-3.8.1-201.fc18.x86_64 @updates Install kernel-3.8.3-203.fc18.x86_64 @updates Erase kernel-devel-3.8.1-201.fc18.x86_64 @updates Install kernel-devel-3.8.3-203.fc18.x86_64 @updates Updated kernel-headers-3.8.3-201.fc18.x86_64 @updates Update 3.8.3-203.fc18.x86_64 @updates Updated llvm-libs-3.1-13.1.fc18.x86_64 @updates Update 3.2-2.fc18.x86_64 @updates Updated mesa-dri-drivers-9.0.3-1.fc18.x86_64 @updates Update 9.1-1.fc18.x86_64 @updates Updated mesa-dri-filesystem-9.0.3-1.fc18.x86_64 @updates Update 9.1-1.fc18.x86_64 @updates Updated mesa-libEGL-9.0.3-1.fc18.i686 @updates Updated mesa-libEGL-9.0.3-1.fc18.x86_64 @updates Update 9.1-1.fc18.i686 @updates Update 9.1-1.fc18.x86_64 @updates Updated mesa-libGL-9.0.3-1.fc18.i686 @updates Updated mesa-libGL-9.0.3-1.fc18.x86_64 @updates Update 9.1-1.fc18.i686 @updates Update 9.1-1.fc18.x86_64 @updates Updated mesa-libgbm-9.0.3-1.fc18.i686 @updates Updated mesa-libgbm-9.0.3-1.fc18.x86_64 @updates Update 9.1-1.fc18.i686 @updates Update 9.1-1.fc18.x86_64 @updates Updated mesa-libglapi-9.0.3-1.fc18.i686 @updates Updated mesa-libglapi-9.0.3-1.fc18.x86_64 @updates Update 9.1-1.fc18.i686 @updates Update 9.1-1.fc18.x86_64 @updates Updated mesa-libxatracker-9.0.3-1.fc18.x86_64 @updates Update 9.1-1.fc18.x86_64 @updates Updated nmap-ncat-2:6.01-9.fc18.x86_64 @updates Update 2:6.25-1.fc18.x86_64 @updates Updated policycoreutils-2.1.13-55.fc18.x86_64 @updates Update 2.1.13-56.fc18.x86_64 @updates Updated policycoreutils-devel-2.1.13-55.fc18.x86_64 @updates Update 2.1.13-56.fc18.x86_64 @updates Updated policycoreutils-gui-2.1.13-55.fc18.x86_64 @updates Update 2.1.13-56.fc18.x86_64 @updates Updated policycoreutils-python-2.1.13-55.fc18.x86_64 @updates Update 2.1.13-56.fc18.x86_64 @updates Updated policycoreutils-restorecond-2.1.13-55.fc18.x86_64 @updates Update 2.1.13-56.fc18.x86_64 @updates Updated policycoreutils-sandbox-2.1.13-55.fc18.x86_64 @updates Update 2.1.13-56.fc18.x86_64 @updates Updated poppler-data-0.4.5-6.fc18.noarch @fedora Update 0.4.6-2.fc18.noarch @updates Updated procps-ng-3.3.3-2.20120807git.fc18.x86_64 @fedora Update 3.3.3-3.20120807git.fc18.x86_64 @updates Updated telepathy-gabble-0.16.4-3.fc18.x86_64 @updates Update 0.16.5-1.fc18.x86_64 @updates Updated tigervnc-license-1.2.80-0.9.20130307svn5060.fc18.noarch @updates Update 1.2.80-0.10.20130314svn5065.fc18.noarch @updates Updated tigervnc-server-minimal-1.2.80-0.9.20130307svn5060.fc18.x86_64 @updates Update 1.2.80-0.10.20130314svn5065.fc18.x86_64 @updates Updated tzdata-2012j-1.fc18.noarch @fedora Update 2013b-1.fc18.noarch @updates Updated tzdata-java-2012j-1.fc18.noarch @fedora Update 2013b-1.fc18.noarch @updates Updated usbutils-006-2.fc18.x86_64 @fedora Update 006-4.fc18.x86_64 @updates history info
Thank you for the update, if it happens again please try to trace the process with strace, both abrtd and gdb, so we can investigate it. $ strace -p<pid of abrt> -ologabrt $ strace -p<pid of gdb> -ologgdb - this should create logabrt and loggdb files I will close this bug if it won't happen again in next 2 weeks.