Bug 1697209

Summary: [abrt] 0ad: std::__replacement_assert(): pyrogenesis killed by SIGABRT
Product: [Fedora] Fedora Reporter: holsteynjohan
Component: 0adAssignee: Paulo Andrade <paulo.cesar.pereira.de.andrade>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: bioinfornatics, cheese, elexis1987, igor.raits, paulo.cesar.pereira.de.andrade, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a7f4e2afd3af4bc1986ff09d8cf52babde9fc0c3
Whiteboard: abrt_hash:18fb584f60952cf080490c38a9d84b61331ea860;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 23:26:19 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

Description holsteynjohan 2019-04-08 05:18:37 UTC
Version-Release number of selected component:
0ad-0.0.23b-1.fc29

Additional info:
reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/bin/pyrogenesis
crash_function: std::__replacement_assert
executable:     /usr/bin/pyrogenesis
journald_cursor: s=f9db6c4698214eaaa506754328a1758f;i=29e671;b=0e8eeccce84c4c5aa3398655cbb96141;m=1295b98ca9;t=585f219890def;x=334d5cea13f46698
kernel:         5.0.5-200.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 holsteynjohan 2019-04-08 05:18:41 UTC
Created attachment 1553371 [details]
File: backtrace

Comment 2 holsteynjohan 2019-04-08 05:18:42 UTC
Created attachment 1553372 [details]
File: cgroup

Comment 3 holsteynjohan 2019-04-08 05:18:45 UTC
Created attachment 1553373 [details]
File: core_backtrace

Comment 4 holsteynjohan 2019-04-08 05:18:46 UTC
Created attachment 1553374 [details]
File: cpuinfo

Comment 5 holsteynjohan 2019-04-08 05:18:47 UTC
Created attachment 1553375 [details]
File: dso_list

Comment 6 holsteynjohan 2019-04-08 05:18:49 UTC
Created attachment 1553376 [details]
File: environ

Comment 7 holsteynjohan 2019-04-08 05:18:50 UTC
Created attachment 1553377 [details]
File: limits

Comment 8 holsteynjohan 2019-04-08 05:18:52 UTC
Created attachment 1553378 [details]
File: maps

Comment 9 holsteynjohan 2019-04-08 05:18:54 UTC
Created attachment 1553379 [details]
File: mountinfo

Comment 10 holsteynjohan 2019-04-08 05:18:56 UTC
Created attachment 1553380 [details]
File: open_fds

Comment 11 holsteynjohan 2019-04-08 05:18:57 UTC
Created attachment 1553381 [details]
File: proc_pid_status

Comment 12 elexis1987 2019-09-17 21:45:20 UTC
For reference, this was reported by a Fedora 29 user on #0ad-dev.

He said it happened occasionally when ending a 0ad match when opening the summary screen and reproducibly when opening the singleplayer gamesetup page, selecting the maptype "random", then clicking on the color dropdown.
The latter results exactly in the CDropdown.cpp stack uploaded here.

I've reported a ticket on the 0ad bugtracker at https://trac.wildfiregames.com/ticket/5598

Comment 13 Ben Cotton 2019-10-31 18:49:59 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 14 Ben Cotton 2019-11-27 23:26:19 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.