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.
Bug 1012827 - deadlock in Garbage Collection Start Event callback
Summary: deadlock in Garbage Collection Start Event callback
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: abrt-java-connector
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Jakub Filak
QA Contact: Lukáš Zachar
URL:
Whiteboard:
: 1020711 1023157 (view as bug list)
Depends On: 1012545
Blocks: 1018804 1020711
TreeView+ depends on / blocked
 
Reported: 2013-09-27 08:36 UTC by Jakub Filak
Modified: 2016-12-01 00:45 UTC (History)
7 users (show)

Fixed In Version: abrt-java-connector-1.0.6-1.el7
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Important: if this rebase instead contains *only bug fixes,* or *only enhancements*, select the correct option from the Doc Type drop-down list. Rebase package(s) to version: 1.0.6 Highlights, important fixes, or notable enhancements: Makes the implementation more thread safe and disables experimental features.
Clone Of: 1012545
Environment:
Last Closed: 2014-06-13 12:06:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jakub Filak 2013-09-27 08:36:01 UTC 
+++ This bug was initially created as a clone of Bug #1012545 +++

Description of problem:
All abrt-java-connector event callbacks enter a single private critical section. Some callbacks may trigger a GC run while being in the critical section. The GC start callback also wants to enter the critical section but the critical section is locked because the triggering callback waits until the GC run finishes. So both callbacks are waiting for each other.

Version-Release number of selected component (if applicable):
abrt-java-connector-1.0.5-1.fc19

How reproducible:
Accidentally

Steps to Reproduce:
1. run a sufficiently big application for a sufficiently long time

--- Additional comment from Jakub Filak on 2013-09-26 17:48:32 CEST ---

A full backtrace of a deadlock between callback_on_gc_start and callback_on_object_alloc
Comment 3 jiri vanek 2013-10-31 09:02:45 UTC 
*** Bug 1023157 has been marked as a duplicate of this bug. ***
Comment 5 Nathan Kinder 2013-11-01 21:24:16 UTC 
*** Bug 1020711 has been marked as a duplicate of this bug. ***
Comment 7 Ludek Smid 2014-06-13 12:06:15 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.