adoptium / adoptium/adoptium-support
eclipse frequent crashes in JRE
- Dominant language
- No language data
- Stars
- 59
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
### Please provide a brief summary of the bug
Random, intermittent crashes of eclipse. Sometimes crashes when there is no user interaction occurring. Sometimes multiple crashes per day, sometimes can go multiple days without an issue. No detectable cause or way to reproduce it. Crash log attached.
Eclipse build ID information:
Eclipse IDE for C/C++ Developers (includes Incubating components)
Version: 2023-06 (4.28.0)
Build id: 20230608-1333
OS: Linux, v.3.10.0-957.27.2.el7.x86_64, x86_64 / gtk 3.22.30
Java vendor: Eclipse Adoptium
Java runtime version: 17.0.7+7
Java version: 17.0.7
[hs_err_pid113068.log](https://github.com/adoptium/adoptium-support/files/12443223/hs_err_pid113068.log)
The crashes started to happen about 4 months ago on an older version of Eclipse. Unknown cause.
### Please provide steps to reproduce where possible
_No response_
### Expected Results
No crashes.
### Actual Results
Eclipse freezes, writes out some crash log and exits.
### What Java Version are you using?
openjdk version "1.8.0_222" OpenJDK Runtime Environment (build 1.8.0_222-b10) OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode)
### What is your operating system and platform?
Linux woodstp-rmd 3.10.0-957.27.2.el7.x86_64 #1 SMP Mon Jul 29 17:46:05 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
### How did you install Java?
Unknown
### Did it work before?
Yes, up until about 4 months ago.
### Did you test with the latest update version?
Yes (latest version of eclipse)
### Did you test with other Java versions?
No
### Relevant log output
_No response_
Contributor guide
Research direction
Start by inspecting the attached hs_err_pid113068.log and the Eclipse, Java, GTK, and Linux versions recorded in the issue. Check whether the crash log identifies a JVM or native component, then compare behavior with other Java versions or a controlled Eclipse setup. Done means identifying a reproducible cause or a sufficiently specific component and diagnostic path; the report currently provides no reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100