Bug 1271342
Summary: | JVM running Eclipse crashes several times per day | ||
---|---|---|---|
Product: | Red Hat Developer Toolset | Reporter: | Levente Farkas <lfarkas> |
Component: | eclipse | Assignee: | Mat Booth <mat.booth> |
Status: | CLOSED ERRATA | QA Contact: | Václav Kadlčík <vkadlcik> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | akurtako, mat.booth, mbenitez, vkadlcik |
Target Milestone: | alpha | ||
Target Release: | 4.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | devtoolset-4-eclipse-4.5.1-7.1.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-31 08:41:24 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: |
Description
Levente Farkas
2015-10-13 17:07:34 UTC
I believe this will be fixed in DTS 4.1, certainly the patch cited above is present in Mars.1 any estimate for DTS 4.1? since currently even devtoolset-4's eclipse package still not released:-( anyway i'd be hapy to test these rpms too:-) (In reply to Levente Farkas from comment #2) > any estimate for DTS 4.1? since currently even devtoolset-4's eclipse > package still not released:-( > anyway i'd be hapy to test these rpms too:-) DTS releases approximately every 6 months. DTS 4.1 is expected some time in the Spring. Unfortunately we can not comment on any more specific dates. (In reply to Levente Farkas from comment #2) > any estimate for DTS 4.1? since currently even devtoolset-4's eclipse > package still not released:-( > anyway i'd be hapy to test these rpms too:-) Hmm, DTS 4.0 should be available: http://developerblog.redhat.com/2015/11/17/gcc-5-developer-toolset-4-generally-available/ verified in the second DTS 4.1 alpha hand-off Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2016:1145 |