https://bugzilla.redhat.com/show_bug.cgi?id=1689037
Michael Catanzaro mcatanza@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jkonecny@redhat.com, | |mcatanza@redhat.com Component|gtk3 |anaconda Assignee|mclasen@redhat.com |anaconda-maint-list@redhat. | |com
--- Comment #44 from Michael Catanzaro mcatanza@redhat.com --- Again, this is memory corruption, so the provided backtraces are not actionable and do not indicate anything wrong in GTK. I've seen crashes in gtk_css_static_style_compute_value() many times and it *always* turns out to be the application corrupting memory somehow. The GTK CSS machinery shows up in the backtrace just because it gets called very frequently, but the game was lost much earlier when the memory corruption first occurred.
Moving this back to anaconda for now, as that's the only reasonable component to use until we know where the memory corruption is actually occurring. I doubt the problem is somewhere in anaconda's codebase, because anaconda is written in python, but until we know where the memory corruption is coming from, there's no better component to assign the bug to. The problem could be anywhere in any library that anaconda uses (most likely), or in the python interpreter itself (much less likely). It could even be somewhere in GTK (just not where the backtrace is pointing to). We're not going to find out without either (a) running anaconda under valgrind, or (b) asan builds of everything (python and every library anaconda links to). Obviously (a) would be easier.
i18n-bugs@lists.fedoraproject.org