Bug 1483066 - packagekitd 100% CPU usage
Summary: packagekitd 100% CPU usage
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-18 17:15 UTC by Germano Massullo
Modified: 2018-06-01 15:15 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:38:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Germano Massullo 2017-08-18 17:15:39 UTC
I am experiencing packagekitd hanging on 100% CPU usage
PackageKit-1.1.6-2.fc26.x86_64

Here is the backtrace

# gdb packagekitd 2118
GNU gdb (GDB) Fedora 8.0-20.fc26
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
packagekitd: No such file or directory.
Attaching to process 2118
[New LWP 2119]
[New LWP 2120]
[New LWP 8543]

warning: .dynamic section for "/lib64/libsqlite3.so.0" is not at the expected address (wrong library or version mismatch?)

warning: .dynamic section for "/lib64/libgdk_pixbuf-2.0.so.0" is not at the expected address (wrong library or version mismatch?)

warning: .dynamic section for "/lib64/libexpat.so.1" is not at the expected address (wrong library or version mismatch?)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x00007fdc58f0ba9d in poll () at ../sysdeps/unix/syscall-template.S:84
84      T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
Missing separate debuginfos, use: dnf debuginfo-install gdk-pixbuf2-2.36.8-1.fc26.x86_64
(gdb) thread apply all backtrace

Thread 4 (Thread 0x7fdc4f04b700 (LWP 8543)):
#0  0x00007fdc58e90428 in _int_malloc (av=av@entry=0x7fdc20000020, bytes=bytes@entry=1048576) at malloc.c:3569
#1  0x00007fdc58e956d8 in __libc_calloc (n=<optimized out>, elem_size=<optimized out>) at malloc.c:3236
#2  0x00007fdc4c718d4b in fprintf (__fmt=0x7fdc4c751d98 "on elements: %d\n", __stream=0x7fdc203994e0) at /usr/include/bits/stdio2.h:97
#3  0x00007fdc4c718d4b in solv_oom (num=126, len=140583406405704) at /usr/src/debug/libsolv-0.6.28/src/util.c:22
#4  0x00007fdc4c718cae in repopagestore_read_or_setup_pages (store=0x7fdc2001b200, fp=0x7fdc209ebff0, pagesz=<optimized out>, blobsz=<optimized out>)
    at /usr/src/debug/libsolv-0.6.28/src/repopage.c:820
#5  0x0000000000000000 in  ()

Thread 3 (Thread 0x7fdc4f84c700 (LWP 2120)):
#0  0x00007fdc58f0ba9d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007fdc59658569 in g_main_context_poll (priority=<optimized out>, n_fds=2, fds=0x7fdc400010c0, timeout=<optimized out>, context=0x5597f5740500) at gmain.c:4271
#2  0x00007fdc59658569 in g_main_context_iterate (context=0x5597f5740500, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3967
#3  0x00007fdc59658902 in g_main_loop_run (loop=0x5597f5742b10) at gmain.c:4168
#4  0x00007fdc59c3dcb6 in gdbus_shared_thread_func (user_data=0x5597f57404d0) at gdbusprivate.c:252
#5  0x00007fdc5967f536 in g_thread_proxy (data=0x5597f57360a0) at gthread.c:784
#6  0x00007fdc591df36d in start_thread (arg=0x7fdc4f84c700) at pthread_create.c:456
#7  0x00007fdc58f17b8f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 2 (Thread 0x7fdc5004d700 (LWP 2119)):
#0  0x00007fdc58f0ba9d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007fdc59658569 in g_main_context_poll (priority=<optimized out>, n_fds=2, fds=0x7fdc480008c0, timeout=<optimized out>, context=0x5597f5735ae0) at gmain.c:4271
#2  0x00007fdc59658569 in g_main_context_iterate (context=context@entry=0x5597f5735ae0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3967
---Type <return> to continue, or q <return> to quit---
#3  0x00007fdc5965867c in g_main_context_iteration (context=0x5597f5735ae0, may_block=may_block@entry=1) at gmain.c:4033
#4  0x00007fdc596586c1 in glib_worker_main (data=<optimized out>) at gmain.c:5824
#5  0x00007fdc5967f536 in g_thread_proxy (data=0x5597f5736000) at gthread.c:784
#6  0x00007fdc591df36d in start_thread (arg=0x7fdc5004d700) at pthread_create.c:456
#7  0x00007fdc58f17b8f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 1 (Thread 0x7fdc5a9b1d80 (LWP 2118)):
#0  0x00007fdc58f0ba9d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007fdc59658569 in g_main_context_poll (priority=<optimized out>, n_fds=3, fds=0x5597f591cd40, timeout=<optimized out>, context=0x5597f571d310) at gmain.c:4271
#2  0x00007fdc59658569 in g_main_context_iterate (context=0x5597f571d310, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3967
#3  0x00007fdc59658902 in g_main_loop_run (loop=0x5597f571cfb0) at gmain.c:4168
#4  0x00005597f39ca3eb in main (argc=<optimized out>, argv=<optimized out>) at pk-main.c:256

Comment 1 Fedora End Of Life 2018-05-03 08:13:58 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Casey Stone 2018-05-08 08:05:12 UTC
I just installed Fedora Workstation 28 from scratch, and today I notice packagekitd is using 100% cpu, current cpu time as shown in top is 462:11.43. It is running as root process 1509 and CANNOT BE KILLED!

Comment 3 Fedora End Of Life 2018-05-29 11:38:14 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 RobbieTheK 2018-06-01 14:46:02 UTC
Can this be reopened for Fedora 28?  4.16.9-300.fc28.x86_64

5998 root      20   0  711560  99560  16152 S  99.0  0.4   1242:56 packagekitd

gdb packagekitd 5998
GNU gdb (GDB) Fedora 8.1-15.fc28
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
packagekitd: No such file or directory.
Attaching to process 5998
[New LWP 5999]
[New LWP 6000]
[New LWP 6650]
[New LWP 7264]

warning: .dynamic section for "/lib64/librpmio.so.8" is not at the expected address (wrong library or version mismatch?)
Missing separate debuginfo for /lib64/libpackagekit-glib2.so.18
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/c4/../../../../../usr/lib/debug/usr/lib64/libpackagekit-glib2.so.18.1.3-1.1.10-1.fc28.x86_64.debug

warning: Loadable section ".note.gnu.property" outside of ELF segments
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x00007f4148a8240c in pthread_setcanceltype (type=603979808, oldtype=0x80)
    at forward.c:200
200	FORWARD (pthread_setcanceltype, (int type, int *oldtype), (type, oldtype), 0)

Comment 5 Rex Dieter 2018-06-01 15:15:51 UTC
I recommend opening a new bug instead


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