Bug 672442 - [abrt] java-1.6.0-openjdk-devel-1:1.6.0.0-50.1.9.4.fc14: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/bin/java was killed by signal 11 (SIGSEGV)
Summary: [abrt] java-1.6.0-openjdk-devel-1:1.6.0.0-50.1.9.4.fc14: Process /usr/lib/jvm...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:aeb67e7e8c47fa8a7b992f39290...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-25 05:14 UTC by Bob Gustafson
Modified: 2011-01-25 20:48 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-25 20:48:14 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (166.09 KB, text/plain)
2011-01-25 05:14 UTC, Bob Gustafson
no flags Details

Description Bob Gustafson 2011-01-25 05:14:22 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/bin/java -Xms32m -Xmx1024m -XX:MaxPermSize=150m -ea -Dconsole.encoding=UTF-8 -Xbootclasspath/a:../lib/boot.jar -Didea.platform.prefix=Ruby -Didea.no.jre.check=true -Djb.restart.code=88 com.intellij.idea.Main
component: java-1.6.0-openjdk
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/bin/java
kernel: 2.6.35.10-74.fc14.x86_64
package: java-1.6.0-openjdk-devel-1:1.6.0.0-50.1.9.4.fc14
reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/bin/java was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1295925058
uid: 500

comment
-----
One issue is that the RubyMine developers don't officially support openJDK. Only 'real' Java.

(see a prior issue I had with RubyMine      http://devnet.jetbrains.net/thread/293348
Copy/Paste works within RubyMine, but the clipboard is empty when trying to paste into a vim edit file outside of RubyMine)

The combination of openJDK and RedMine occasionally shows some flakeyness - In debug mode, sometimes the 'watch' variables are not the correct variables (name syncing..), but RubyMine debug does recover in a few more steps. This may be due to problems within RubyMine code, or problems within openJDK code - don't know, but I would be willing to provide tests and screen dumps if you are interested (This is a separate problem - probably not related to this bug)

RubyMine has never crashed on me. I have never lost any files while within RubyMine - and the services provided by RubyMine are quite useful (and superb in spots). An active collaboration between openJDK developers and RubyMine could be useful.

It is an interesting test - whether open source development can 'win' against commercial interests (Java under Oracle control)..

How to reproduce
-----
1. I had just rebooted my system
2. This was the first time since the reboot that RubyMine was started.
3. Before the reboot, I had been using RubyMine to debug a Ruby on Rails application
4. I had downloaded and installed some updates to the F14 system.
5. The updates had required a reboot (restart)
6. I basically resumed my debugging where I left off prior to the reboot.

Comment 1 Bob Gustafson 2011-01-25 05:14:29 UTC
Created attachment 475108 [details]
File: backtrace

Comment 2 Deepak Bhole 2011-01-25 18:19:02 UTC
Hi. Unfortunately the attached stack trace does not contain enough information to track the problem. Was this a one time error or are you seeing this consistently?

Comment 3 Bob Gustafson 2011-01-25 19:49:03 UTC
I'm disappointed that the stack trace did not contain useful information.

When I clicked on 'prepare the report..' it said it needed to download 143 debug enabled files for the various parts. I went to dinner and after I came back, it was ready for my comments and the 'send' click.

----

The Copy/Paste problem is consistent.

The crash seemed to be a one-time problem - possibly related to the system reboot and restart of RubyMines. I would guess that there are some uninitialized pointers involved in the crash.

Comment 4 Deepak Bhole 2011-01-25 20:48:14 UTC
Ah, that is too bad. I will close this bug for now, but please feel free to re-open it if it happens again.


Note You need to log in before you can comment on or make changes to this bug.