Bug 576418 - Extremely Slow Performance
Summary: Extremely Slow Performance
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jiri Moskovcak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-23 23:52 UTC by David Le Sage
Modified: 2015-02-01 22:51 UTC (History)
8 users (show)

Fixed In Version: abrt-1.1.13-1.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-17 05:28:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Le Sage 2010-03-23 23:52:00 UTC
Description of problem:
I am running a Fedora 13 alpha build.  I have triggered a crash in an application that I wish to report via abrt.  Unfortunately, it is running at an extremely slow speed, taking well over an hour to dowload 14 debug packages, (in contrast to Yum, which pulls down large updates in moments.)  Even after all of the debugging information is downloaded and unpacked, it took another 20-30 minutes for abrt to process it and reach the stage where it was ready to provide a backtrace to report.  

Version-Release number of selected component (if applicable):
abrt 1.0.8 (Fedora 13 alpha)

How reproducible:
Every time.

Steps to Reproduce:
1. Generate a crash.
2. Choose to report it with abrt.
  
Actual results:
Extremely slow to download debug packages and then to generate a backtrace.

Expected results:
Download speed should be comparable to Yum.   (Note I am in the same building as the Brisbane repo mirror, so Yum is normally extremely fast for me.)

Additional info:

Comment 1 Denys Vlasenko 2010-03-24 13:03:02 UTC
Please restart abrtd in foreground in verbose mode so that you can see and save entire log:

killall abrtd
abrtd -dvvv 2>&1 | tee LOG

then run 

abrt-gui -v

Then [Report] a crash, and press [Refresh] in report dialog. When you see "Getting list of build IDs", llok into abrtd's log.

You will see something like

abrt-debuginfo-install /var/cache/abrt/ccpp-1269022646-17021/coredump /var/run/abrt/tmp-4443-1269435340 /var/cache/abrt-di

Copy and save this command, then cancel and close abrt-gui (we don't need it anymore). You can rerun the command by hand to debug the problem. Example:

# abrt-debuginfo-install /var/cache/abrt/ccpp-1269022646-17021/coredump /var/run/abrt/tmp-4443-1269435340 /var/cache/abrt-di
Getting list of build IDs
4 missing debuginfos, getting package list from cache
4 missing debuginfos, getting package list from repositories
MISSING:0b854fd13cf401c6f9ad85625d81dcf694a0c10a
MISSING:3b5ce96aac4bb0936b652bff73050db44d60045a
MISSING:c0c63a08fa125acd0af55898673fc142332e7018
MISSING:f3b18818e0c33321a8152c9d853ee84ff00bc85d
4 debuginfos can't be found

/usr/bin/abrt-debuginfo-install is a shell script. Please edit it, replacing debug=false by debug=true here:

core="$1"
tempdir="$2"
debuginfodirs="${3//:/ }"
cachedir="${3%%:*}"
debug=false    <======================== HERE
# Useful if you need to see saved rpms, command outputs etc
keep_tmp=false

Then rerun abrt-debuginfo-install command saved before and post the log here.
In my example, I am getting this:

# abrt-debuginfo-install /var/cache/abrt/ccpp-1269022646-17021/coredump /var/run/abrt/tmp-4443-1269435340 /var/cache/abrt-di
Downloading rpms to /var/run/abrt/tmp-4443-1269435340
Getting list of build IDs
build_ids:0b854fd13cf401c6f9ad85625d81dcf694a0c10a 3b5ce96aac4bb0936b652bff73050db44d60045a 6bd8a3aaff2dae749bbaf421b8962d67d63b0cfd c0c63a08fa125acd0af55898673fc142332e7018 f3b18818e0c33321a8152c9d853ee84ff00bc85d
missing_debuginfo_files:/usr/lib/debug/.build-id/0b/854fd13cf401c6f9ad85625d81dcf694a0c10a.debug /usr/lib/debug/.build-id/3b/5ce96aac4bb0936b652bff73050db44d60045a.debug /usr/lib/debug/.build-id/c0/c63a08fa125acd0af55898673fc142332e7018.debug /usr/lib/debug/.build-id/f3/b18818e0c33321a8152c9d853ee84ff00bc85d.debug 
4 missing debuginfos, getting package list from cache
Running: yum -C '--disablerepo=*' '--enablerepo=adobe-linux-i386-debuginfo*' '--enablerepo=fedora-debuginfo*' '--enablerepo=rpmfusion-free-debuginfo*' '--enablerepo=rpmfusion-free-updates-debuginfo*' '--enablerepo=rpmfusion-nonfree-debuginfo*' '--enablerepo=rpmfusion-nonfree-updates-debuginfo*' '--enablerepo=updates-debuginfo*' --showduplicates --quiet provides /usr/lib/debug/.build-id/0b/854fd13cf401c6f9ad85625d81dcf694a0c10a.debug /usr/lib/debug/.build-id/3b/5ce96aac4bb0936b652bff73050db44d60045a.debug /usr/lib/debug/.build-id/c0/c63a08fa125acd0af55898673fc142332e7018.debug /usr/lib/debug/.build-id/f3/b18818e0c33321a8152c9d853ee84ff00bc85d.debug 
packages (1):
missing_debuginfo_files:/usr/lib/debug/.build-id/0b/854fd13cf401c6f9ad85625d81dcf694a0c10a.debug /usr/lib/debug/.build-id/3b/5ce96aac4bb0936b652bff73050db44d60045a.debug /usr/lib/debug/.build-id/c0/c63a08fa125acd0af55898673fc142332e7018.debug /usr/lib/debug/.build-id/f3/b18818e0c33321a8152c9d853ee84ff00bc85d.debug 
4 missing debuginfos, getting package list from repositories
Running: yum  '--disablerepo=*' '--enablerepo=adobe-linux-i386-debuginfo*' '--enablerepo=fedora-debuginfo*' '--enablerepo=rpmfusion-free-debuginfo*' '--enablerepo=rpmfusion-free-updates-debuginfo*' '--enablerepo=rpmfusion-nonfree-debuginfo*' '--enablerepo=rpmfusion-nonfree-updates-debuginfo*' '--enablerepo=updates-debuginfo*' --showduplicates --quiet provides /usr/lib/debug/.build-id/0b/854fd13cf401c6f9ad85625d81dcf694a0c10a.debug /usr/lib/debug/.build-id/3b/5ce96aac4bb0936b652bff73050db44d60045a.debug /usr/lib/debug/.build-id/c0/c63a08fa125acd0af55898673fc142332e7018.debug /usr/lib/debug/.build-id/f3/b18818e0c33321a8152c9d853ee84ff00bc85d.debug 
packages (2):
missing_build_ids:0b854fd13cf401c6f9ad85625d81dcf694a0c10a 3b5ce96aac4bb0936b652bff73050db44d60045a c0c63a08fa125acd0af55898673fc142332e7018 f3b18818e0c33321a8152c9d853ee84ff00bc85d 
Removing /var/run/abrt/tmp-4443-1269435340
MISSING:0b854fd13cf401c6f9ad85625d81dcf694a0c10a
MISSING:3b5ce96aac4bb0936b652bff73050db44d60045a
MISSING:c0c63a08fa125acd0af55898673fc142332e7018
MISSING:f3b18818e0c33321a8152c9d853ee84ff00bc85d
4 debuginfos can't be found

You log will be similarly detailed, and will be useful for debugging. Also please indicate after which lines exactly you see large delays.

Comment 2 David Le Sage 2010-03-24 22:45:49 UTC
Thanks for the detailed instructions.  I'll do some research.

Comment 3 Jiri Moskovcak 2010-03-25 09:00:12 UTC
Hi,
what was the crashed application? The coredump processing and creating the backtrace might take really long if it was some big app (e.g. generating ooffice backtrace can take even few hours ...). The abrt-debuginfo-install uses yum and yumdownloader to download the packages, so if the download is slow it's probably some problem with yumdownloader.

J.

Comment 4 David Le Sage 2010-03-25 22:54:52 UTC
Hello Jiri,


Yes, I was doing some research into it last night.  It was an Empathy crash and I have discovered that it was trying to pull down the webkit-gtk library which is 80 mb.  Maybe it was just a case of yumdownloader being unable to contact the Brisbane server and moving to another repo mirror.


I do have yum-plugin-fastestmirror installed.  I presume when abrt calls yumdownloader it knows to use that...

Once the debug libraries were downloaded, it still took an awfully long time, over many minutes, for the backtrace.

Comment 5 David Le Sage 2010-03-26 06:47:11 UTC
I have also found, on running through the log that it was trying to process 


abrtd: Executable '' doesn't belong to any package
abrtd: Corrupted or bad crash /var/cache/abrt/ccpp-1265510829-22289 (res:4), deleting


over and over.  So perhaps it was a combination of that and the large size of the packages involved?

Comment 6 Jiri Moskovcak 2010-05-26 17:49:36 UTC
(In reply to comment #5)
> I have also found, on running through the log that it was trying to process 
> 
> 
> abrtd: Executable '' doesn't belong to any package
> abrtd: Corrupted or bad crash /var/cache/abrt/ccpp-1265510829-22289 (res:4),
> deleting
> 
> 
> over and over.  So perhaps it was a combination of that and the large size of
> the packages involved?    

This isues has been fixed in the recent version 1.1.3+ will make an update asap.

Comment 7 Fedora Update System 2010-08-11 11:17:04 UTC
abrt-1.1.13-1.fc14 has been submitted as an update for Fedora 14.
http://admin.fedoraproject.org/updates/abrt-1.1.13-1.fc14

Comment 8 Fedora Update System 2010-08-12 12:57:58 UTC
abrt-1.1.13-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/abrt-1.1.13-1.fc13

Comment 9 Fedora Update System 2010-08-12 19:52:16 UTC
abrt-1.1.13-1.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update abrt'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/abrt-1.1.13-1.fc14

Comment 10 Fedora Update System 2010-08-16 14:06:37 UTC
abrt-1.1.13-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/abrt-1.1.13-1.fc12

Comment 11 Fedora Update System 2010-08-17 05:26:50 UTC
abrt-1.1.13-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2010-08-20 13:31:14 UTC
abrt-1.1.13-2.fc14 has been submitted as an update for Fedora 14.
http://admin.fedoraproject.org/updates/abrt-1.1.13-2.fc14

Comment 13 Fedora Update System 2010-08-24 01:11:46 UTC
abrt-1.1.13-2.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 14 Fedora Update System 2010-08-24 21:17:28 UTC
abrt-1.1.13-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.