Red Hat Bugzilla – Bug 1012545
deadlock in Garbage Collection Start Event callback
Last modified: 2016-11-30 19:45:11 EST
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):
Steps to Reproduce:
1. run a sufficiently big application for a sufficiently long time
Created attachment 803476 [details]
A full backtrace of a deadlock between callback_on_gc_start and callback_on_object_alloc
Upstream commit d84b4c8883bc145b0afa6b89f025dea1fa98cc3c fixes this bug.
abrt-java-connector-1.0.6-1.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-java-connector-1.0.6-1.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
abrt-java-connector-1.0.6-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.