Bug 822805
Summary: | [abrt] java-1.7.0-openjdk-1.7.0.3-2.1.fc17.6: Process /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.3.x86_64/jre/bin/java was killed by signal 11 (SIGSEGV) | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Krzysztof Daniel <kdaniel> | ||||||||||||||
Component: | java-1.7.0-openjdk | Assignee: | Krzysztof Daniel <kdaniel> | ||||||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||
Priority: | unspecified | ||||||||||||||||
Version: | 17 | CC: | dbhole, ignace.bienville, jvanek, mbenitez, omajid | ||||||||||||||
Target Milestone: | --- | ||||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||
OS: | Unspecified | ||||||||||||||||
Whiteboard: | abrt_hash:cbb55286a968fa94935dc6300dc39c03559a111d | ||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||
Clone Of: | Environment: | ||||||||||||||||
Last Closed: | 2013-08-01 17:18:41 UTC | Type: | --- | ||||||||||||||
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
Krzysztof Daniel
2012-05-18 08:42:46 UTC
Created attachment 585360 [details]
File: open_fds
Created attachment 585361 [details]
File: dso_list
Created attachment 585362 [details]
File: build_ids
Created attachment 585363 [details]
File: var_log_messages
Created attachment 585364 [details]
File: maps
Created attachment 585365 [details]
File: backtrace
Deepak, could you look at this one and tell where to start investigation at Eclipse side? Hi Kris, can you reproduce this? Given that there are only 2 frames, it seems unlikely that the VM could be the cause, more likely that the binary launcher has an issue (assuming Eclipse still uses a binary launcher?) I think I can reproduce this issue on demand. The steps are simple. Install Eclipse and use Eclipse web browser. Eclipse crashes pretty fast after that (although not always). If you run Eclipse and do a ps aux, you should be able to see the full java command it runs. The best first step then is to install the debuginfo for the JDK and run 'java' under GDB with those args to start Eclipse and then make it crash. That should give you the ability to inspect not just the stack, but also the variable values that led to the crash. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |