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:
Is this reproducible? Also, which version of OpenJDK are you using? This does not look like a Fedora version...
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)
Do you have a core stack trace available for this by any chance?
I obtain this file: https://app.box.com/s/fg9nstnftimhm7ept2rb
Re-assigning to Omair to take a look.
I can not reproduce on x86_64. Let me try on i686.
I can't reproduce this locally. Are you still getting this error with the latest updates in Fedora?
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...
Error: could not find libjava.so Error: Could not find Java SE Runtime Environment.
(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 ?
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?
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
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.
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?
Griffon 1.5.0 was released today, tried it and saw that it works fine :-) maybe we close this issue?
Sure, I am closing as WORKSFORME. If you run into an issue again, please reopen with more information. Thanks.