Bug 1651019

Summary: libmodulemd Prioritizer corrupt list crash during Prioritizer destructor
Product: [Fedora] Fedora Reporter: Hin-Tak Leung <htl10>
Component: libmodulemdAssignee: Stephen Gallagher <sgallagh>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: jonathan, klember, rdieter, rhughes, sgallagh, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/dc9af130589cb3cba18f37aeab898aea15a6d465
Whiteboard: abrt_hash:6b22f10e83aa87414a7bfd72e005db85a72bbc0b;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 20:07:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Hin-Tak Leung 2018-11-18 21:18:59 UTC
Description of problem:


Version-Release number of selected component:
PackageKit-1.1.11-1.fc29

Additional info:
reporter:       libreport-2.9.6
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: ptr_array_free
executable:     /usr/libexec/packagekitd
journald_cursor: s=6e0d5a72b9284dc6bb75246527bc10fc;i=d2b04;b=6e2847c100334a6eb7374bf3a62fbcd7;m=2144ee1bdd;t=57adc165c91e6;x=b228f7dd8771ef69
kernel:         4.18.18-300.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Comment 1 Hin-Tak Leung 2018-11-18 21:19:06 UTC
Created attachment 1507027 [details]
File: backtrace

Comment 2 Hin-Tak Leung 2018-11-18 21:19:07 UTC
Created attachment 1507028 [details]
File: cgroup

Comment 3 Hin-Tak Leung 2018-11-18 21:19:09 UTC
Created attachment 1507029 [details]
File: core_backtrace

Comment 4 Hin-Tak Leung 2018-11-18 21:19:10 UTC
Created attachment 1507030 [details]
File: cpuinfo

Comment 5 Hin-Tak Leung 2018-11-18 21:19:12 UTC
Created attachment 1507031 [details]
File: dso_list

Comment 6 Hin-Tak Leung 2018-11-18 21:19:14 UTC
Created attachment 1507032 [details]
File: environ

Comment 7 Hin-Tak Leung 2018-11-18 21:19:16 UTC
Created attachment 1507033 [details]
File: limits

Comment 8 Hin-Tak Leung 2018-11-18 21:19:18 UTC
Created attachment 1507034 [details]
File: maps

Comment 9 Hin-Tak Leung 2018-11-18 21:19:19 UTC
Created attachment 1507035 [details]
File: mountinfo

Comment 10 Hin-Tak Leung 2018-11-18 21:19:21 UTC
Created attachment 1507036 [details]
File: open_fds

Comment 11 Hin-Tak Leung 2018-11-18 21:19:22 UTC
Created attachment 1507037 [details]
File: proc_pid_status

Comment 12 Hin-Tak Leung 2018-11-18 21:19:23 UTC
Created attachment 1507038 [details]
File: var_log_messages

Comment 13 Kalev Lember 2018-11-28 08:50:33 UTC
Looks like a libmodulemd issue. Reassigning.

Comment 14 Stephen Gallagher 2018-11-28 13:14:50 UTC
Yeah, definitely looks like a memory management bug in the libmodulemd Prioritizer object somewhere. I'll see if I can reproduce it.

Comment 15 Ben Cotton 2019-10-31 20:24:15 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'.

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 29 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 16 Ben Cotton 2019-11-27 20:07:06 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.