adoptium / adoptium/adoptium-support

Frequent crash with JDK17 and eclipse

Open
#466 6 comments 0 reactions 0 assignees View on GitHub
bug jbs:needs-report version:17 windows
Dominant language
No language data
Stars
59
Forks
13
PR merge metrics
No merged PRs in 30d

Description

## Summary
Since I upgraded to JDK17, I have frequent and randomly crash when I modify a class in the eclipse IDE and press the save button or sometime when a breakpoint is reached.

I use the WildFly 26 application server

## Steps to reproduce
Modify a class in eclipse and press the save button or sometime when a breakpoint is reached.

## Expected results
No crash

## Actual results
JVM crash frequently when I just change a Java class in eclipse with the message:

> EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff9cb46d69a, pid=11320, tid=11768
>
> JRE version: OpenJDK Runtime Environment Temurin-17.0.2+8 (17.0.2+8) (build 17.0.2+8)
> Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.2+8 (17.0.2+8, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
> Problematic frame:
> V [jvm.dll+0x79d69a]

Always with the same frame: [jvm.dll+0x79d69a]

Two example of crash log:
[hs_err_pid11320.log](https://github.com/adoptium/adoptium-support/files/8168235/hs_err_pid11320.log)
[hs_err_pid12092.log](https://github.com/adoptium/adoptium-support/files/8168236/hs_err_pid12092.log)

## Triaging info

Java version:
openjdk version "17.0.2" 2022-01-18
OpenJDK Runtime Environment Temurin-17.0.2+8 (build 17.0.2+8)
OpenJDK 64-Bit Server VM Temurin-17.0.2+8 (build 17.0.2+8, mixed mode, sharing)

What is your operating system and platform?
Windows 10 21H2

How did you install Java?
I Used the zip version

Did it work before?
No problem with JDK11

Did you test with other Java versions?
I tested version 17.0.1 with the same problem

Contributor guide

Open the contributing guide

Research direction

Start with the two attached hs_err_pid logs and compare the repeated jvm.dll+0x79d69a frame across JDK 17.0.1, 17.0.2, and JDK 11 on Windows 10. A useful resolution would require a reproducible crash or a confirmed affected component/version, followed by verification that the crash no longer occurs.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
developer-experience, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.