Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1132190[details]
ff45 backtrace
Description of problem:
Segfault right after ff start, core file (http://download.eng.brq.redhat.com/scratch/tpelka/ff/core.14347) and backtrace attached.
Version-Release number of selected component (if applicable):
firefox-45.0-0.12.el7_2.aarch64
How reproducible:
100%
Steps to Reproduce:
1. start ff
2.
3.
Actual results:
segfault
Expected results:
should not segfault
Additional info:
I'm not seeing this (immediate) crash with firefox-45.3.0-1.el7_2.aarch64.
I do encounter the (delayed) crash reported in bug 1358441. For that bug, I think I actually have an analysis (no hard proof or patch yet), so I'll continue there. I originally thought this BZ would be a duplicate, but the stack dump in comment 0 here looks very different, so these two are likely not duplicates.
(OTOH, as I said, I can't see *this* kind of crash at all, so maybe we can close this as WORKSFORME, if it stops reproducing for everyone else too.)
Hi Tomas,
if the question is addressed to me, then I don't understand it. As I wrote in comment 5, I couldn't reproduce this specific kind of crash at all, even with "firefox-45.3.0-1.el7_2".
Regarding "firefox-45.4.0-1.el7_2" (which you linked in comment 6): the fix that I prepared for the other bug 1358441 works well on top of firefox-45.4.0-1, so firefox-45.4.0-1 is certainly a good baseline -- with my build I'm not seeing any crashes at all.
If your question is addressed to the other subscribers of this bug, so that we learn whether firefox-45.4.0-1 reproduces this specific bug for them or not, then sorry for the noise.