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.
DescriptionBranislav Blaškovič
2013-11-15 10:39:12 UTC
Description of problem:
I've logged in as root. It just crashed.
Version-Release number of selected component:
yelp-3.8.1-5.el7
Additional info:
reporter: libreport-2.1.7
backtrace_rating: 4
cmdline: yelp help:gnome-help/getting-started
crash_function: _int_free
executable: /usr/bin/yelp
kernel: 3.10.0-49.el7.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 _int_free at /lib64/libc.so.6
#1 JSC::CodeBlock::~CodeBlock() at /lib64/libjavascriptcoregtk-3.0.so.0
#2 JSC::FunctionCodeBlock::~FunctionCodeBlock() at /lib64/libjavascriptcoregtk-3.0.so.0
#3 JSC::FunctionExecutable::clearCode() at /lib64/libjavascriptcoregtk-3.0.so.0
#4 JSC::Heap::deleteUnmarkedCompiledCode() at /lib64/libjavascriptcoregtk-3.0.so.0
#5 JSC::Heap::collect(JSC::Heap::SweepToggle) at /lib64/libjavascriptcoregtk-3.0.so.0
#6 WebCore::collect(void*) at /lib64/libwebkitgtk-3.0.so.0
#7 WebCore::ThreadTimers::sharedTimerFiredInternal() at /lib64/libwebkitgtk-3.0.so.0
#8 WebCore::timeout_cb(void*) at /lib64/libwebkitgtk-3.0.so.0
#9 g_timeout_dispatch at /lib64/libglib-2.0.so.0
Comment 1Branislav Blaškovič
2013-11-15 10:39:15 UTC
Comment 15RHEL Program Management
2014-03-22 06:31:36 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
I suspect that this was just some random crash caught by ABRT. If I'm mistaken and it is reproducible can you please try to reproduce it with on RHEL 7.2 where the webkitgtk3 package was rebased?
Comment 19Branislav Blaškovič
2016-01-21 10:29:09 UTC
I am no longer able to reproduce, so it was most probably random.