Bug 1047004

Summary: OpenJDK crash executing griffon framework
Product: [Fedora] Fedora Reporter: Alex Irmel Oviedo Solis <alleinerwolf>
Component: java-1.7.0-openjdkAssignee: Omair Majid <omajid>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ahughes, alleinerwolf, dbhole, jerboaa, jvanek, omajid
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-13 00:17:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Error report file none

Description Alex Irmel Oviedo Solis 2013-12-28 04:16:34 UTC 
Created attachment 842588 [details]
Error report file

Description of problem:

OpenJDK falls when tries to run the "griffon run-app" command

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install griffon framework. http://griffon.codehaus.org/guide/latest/guide/gettingStarted.html#installing
2. Create a griffon app: griffon create-app Example
3. Change directory to the griffon app directory: cd Example
4. Run the griffon app: griffon run-app

Actual results:
Actually we get this error message:
-----
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGILL (0x4) at pc=0x7c7120ed, pid=2765, tid=2098338624
#
# JRE version: OpenJDK Runtime Environment (7.0_45-b15) (build 1.7.0_45-mockbuild_2013_10_17_16_48-b00)
# Java VM: OpenJDK Server VM (24.45-b08 mixed mode linux-x86 )
# Problematic frame:
# C  0x7c7120ed
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /tmp/jvm-2765/hs_error.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
#   http://icedtea.classpath.org/bugzilla
#
-------

Expected results:
Display a empty window

Additional info:
Comment 1 Deepak Bhole 2014-01-02 16:47:50 UTC 
Is this reproducible? Also, which version of OpenJDK are you using? This does not look like a Fedora version...
Comment 2 Alex Irmel Oviedo Solis 2014-01-02 17:45:09 UTC 
Steps to Reproduce:
===================

1. Install griffon framework. http://griffon.codehaus.org/guide/latest/guide/gettingStarted.html#installing
2. Create a griffon app with: griffon create-app Example
3. Change directory to the griffon app directory: cd Example
4. Run the griffon app: griffon run-app

Actual results:
===============

Actually I get a error message (see the attachment).

Expected results:
=================

Display a empty window with the message "The content goes here"

OpenJDK - Version
=================

Name        : java-1.7.0-openjdk
Arch        : i686
Epoch       : 1
Version     : 1.7.0.60
Release     : 2.4.3.0.fc20

Fedora- Version
===============

Fedora release 20 (Heisenbug)
Comment 3 Deepak Bhole 2014-01-10 21:53:05 UTC 
Do you have a core stack trace available for this by any chance?
Comment 4 Alex Irmel Oviedo Solis 2014-01-11 01:51:45 UTC 
I obtain this file:

https://app.box.com/s/fg9nstnftimhm7ept2rb
Comment 5 Deepak Bhole 2014-01-13 15:38:10 UTC 
Re-assigning to Omair to take a look.
Comment 6 Omair Majid 2014-01-16 21:19:27 UTC 
I can not reproduce on x86_64. Let me try on i686.
Comment 7 Omair Majid 2014-01-20 20:24:37 UTC 
I can't reproduce this locally. Are you still getting this error with the latest updates in Fedora?
Comment 8 Alex Irmel Oviedo Solis 2014-01-20 22:22:45 UTC 
I tried to update and I have a worse problem :-( and I can work now, the installation crash, the system can't find the java executable...
Comment 9 Alex Irmel Oviedo Solis 2014-01-20 22:24:00 UTC 
Error: could not find libjava.so
Error: Could not find Java SE Runtime Environment.
Comment 10 Omair Majid 2014-01-20 22:25:38 UTC 
(In reply to Alex Irmel Oviedo Solis from comment #8)
> I tried to update and I have a worse problem :-( and I can work now, the
> installation crash, the system can't find the java executable...

Did you get hit by https://fedoraproject.org/wiki/Common_F20_bugs#RPM_scriptlets_fail_during_updates ?
Comment 11 jiri vanek 2014-01-21 10:41:41 UTC 
May It be caused by abrt connector?
Alex, do you mind to try two approaches?
1) replace jre/bin/java by jre-abrt/bin/java  (both are in your sdk directroy)
  - you can see that  /jre/bin/java is just script lunching /jre-abrt/bin/java with few more parameters (http://pkgs.fedoraproject.org/cgit/java-1.7.0-openjdk.git/tree/java-abrt-luncher?h=f20)
2) remove all abrt* from test machine and try again?
Comment 12 jiri vanek 2014-01-21 10:45:39 UTC 
just note  -there is xor between 1 and 2, It wil help to  generalise if it is script or abrt agent.
So do one, revert do second and vice versa:) 

(In reply to Alex Irmel Oviedo Solis from comment #8)
> I tried to update and I have a worse problem :-( and I can work now, the
> installation crash, the system can't find the java executable...

May this be related?
https://bugzilla.redhat.com/show_bug.cgi?id=1049015
Comment 13 Alex Irmel Oviedo Solis 2014-02-04 16:17:10 UTC 
I reinstalled the all system and the problem with openjdk-update is fixed, but the problem with the griffon framework and fedora persists. I tried with Oracle's jdk too and get the same problem.
Comment 14 Omair Majid 2014-02-04 16:32:11 UTC 
Can you please 'yum update', run griffon and post the generated core file somewhere? A backtrace from gdb will be just fine too.

Any chance you can reproduce this in a VM?
Comment 15 Alex Irmel Oviedo Solis 2014-02-13 00:13:41 UTC 
Griffon 1.5.0 was released today, tried it and saw that it works fine :-) maybe we close this issue?
Comment 16 Omair Majid 2014-02-13 00:17:44 UTC 
Sure, I am closing as WORKSFORME. If you run into an issue again, please reopen with more information.

Thanks.