Bug 1627954
| Summary: | Crash in libdnf hy_repo_get_string while auto-refreshing updates (I think) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> | ||||||
| Component: | PackageKit | Assignee: | Richard Hughes <rhughes> | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 31 | CC: | dmach, ignatenko, jonathan, klember, rdieter, rhughes, sgallagh, smparrish | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-11-03 22:33:23 UTC | Type: | Bug | ||||||
| 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
Adam Williamson
2018-09-12 00:32:23 UTC
Leaving assigned to PK for now, but CCing libdnf folks. "nevraTuple = std::tuple containing = {
[1] = std::vector of length -4389590794240, capacity 112223571 = {
<error reading variable nevraTuple (Cannot access memory at address 0x7fc100000000)>" looks odd.
Created attachment 1482515 [details]
backtrace of the crash
Note this crash doesn't appear to happen *all* the time - I restarted the test and it worked OK. Same crash in a different test here: https://openqa.fedoraproject.org/tests/278449 that test is trying to test update notification, but looks like the same crash happened there too. CCing sgallagh as this looks like it's in modularity bits... I'm going to need a proper coredump and/or consistent reproduction steps for this. I've been trying to reproduce it locally, but I'm having no luck. The backtrace was already generated from a coredump, what more are you going to do with it? You can download it from the 'Assets' tab of the openQA test if you need it, though: https://openqa.fedoraproject.org/tests/278254/file/desktop_update_graphical-spoolabrt.tar.gz (the abrt problem directory, including the coredump) (In reply to Adam Williamson from comment #8) > The backtrace was already generated from a coredump, what more are you going > to do with it? You can download it from the 'Assets' tab of the openQA test > if you need it, though: > > https://openqa.fedoraproject.org/tests/278254/file/desktop_update_graphical- > spoolabrt.tar.gz (the abrt problem directory, including the coredump) Since the issue appears to be due to memory corruption, I want to inspect the variables to try and track down what got freed (or not initialized). The backtrace doesn't give me enough to go on, unfortunately. Thanks for the link; I'll load that up and get back to you. Created attachment 1483108 [details]
abrt crash problem directory (inc. coredump)
Attaching the abrt problem directory tarball for posterity (it'll get cleaned up from openQA in a while).
Is this issue still happening on Rawhide? For whatever reason, that coredump was useless and even when I had the matching debuginfo and debugsource packages, GDB was pointing at memory areas that didn't match the extracted coredump. I haven't been able to reproduce the issue, but I'm wondering if the recent libdnf changes might have fixed it for us. This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'. This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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. Don't think we've seen this issue lately. |