GNOME Bugzilla – Bug 321296
bug-buddy hangs when updating system information, using 100% CPU
Last modified: 2006-10-01 03:56:43 UTC
Please describe the problem: When an application crashes and I choose "inform developers" (or something like that, I have a German system), bug-buddy appears and says that it collects information concerning the crash. It then uses 100 % CPU to collect the data (i.e. to make a stacktrace), however, it doesn't get finished ever. I let it run for an hour but it did not finish. Steps to reproduce: 1. Let an application crash (shouldn't be too difficult with Nautilus ;)) 2. "Inform developers" Actual results: bug-buddy hangs when making a backtrace with 100% CPU utilisation. It also reacts very very slow. Expected results: I would expect it to finish the backtrace and let me report the bug. Does this happen every time? YES! I can't report bugs using bug-buddy because of this bug. Other information: Ubuntu 5.10/AMD64 AMD Athlon64 3200+, 1 GB RAM, enough free disk space
Created attachment 54668 [details] Backtrace details These details appear when I select "show details" in the "collecting information" dialog. I think the list is always getting longer while bug-buddy works, but it doesn't finish. It's not easy to get this list because "select all" and "copy to clipboard" takes 10 sec each (bug-buddy reacts very slow)
I tried to get a backtrace via gdb now, and funnily, "thread apply all bt" after crashing Nautilus results in a stacktrace which is several hundred lines long and even longer (I aborted with q<enter>). Maybe this bug is caused by gdb by producing endless stack traces?
Any idea why this error occurs or for a workaround? I would like to report so many bugs and I can't because the bug buddy or gdb is so buggy...
This backtrace comes from nautilus process. We would need a backtrace from bug-buddy while it is hanging.
Backtrace while bug-buddy is "hanging", i.e. collecting info from gdb: $ gdb bug-buddy <pid> ... (gdb) thread apply all bt
+ Trace 67030
Thread 1 (Thread 46912584315744 (LWP 14077))
Maybe this is useful, too (gdb is called from bug-buddy): $ ps ax ... 13563 ? Sl 0:00 /usr/lib/evolution/2.4/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Excha14071 ? S 0:00 /usr/bin/evolution mailto:a@test.com, b@x.com?attach=/home/devvv/Entwicklung/java/YC/YCGUI.java 14076 ? S 0:00 /usr/lib/libgnomeui-0/gnome_segv evolution 11 2.4.1 14081 ? R 0:30 /usr/bin/gdb --batch --quiet --command=/usr/share/bug-buddy/gdb-cmd /usr/bin/evolution 14010 14010 ? Tl 0:02 /usr/bin/evolution mailto:test@test.at,lol@lol.at?attach=/home/devvv/Entwicklung/java/YC/yc.log 14083 ? Z 0:00 [gdb] <defunct> 14077 ? S 0:01 /usr/bin/bug-buddy --appname=evolution --pid=14010 --package-ver=2.4.1 14117 pts/0 R+ 0:00 ps ax
*** Bug 316859 has been marked as a duplicate of this bug. ***
I assume it cannot reach bugzilla.gnome.org for some reason. Can you check with Bug-Buddy 2.15.0 or newer? It doesn't need the server information, so this should be gone.
Closing this bug report as no further information has been provided. Bernhard, please feel free to reopen this bug if you can still reproduce this with version 2.1.50 or newer. Thanks a lot in advance!