adoptium / adoptium/adoptium-support

The crash happened outside the Java Virtual Machine in native code.

Open
#883 2 comments 0 reactions 0 assignees View on GitHub
bug jbs:needs-report
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

#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffd5eb23119, pid=4152, tid=12252
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.7+7 (17.0.7+7) (build 17.0.7+7)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.7+7 (17.0.7+7, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C [libtesseract53.dll+0x13119]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\mhiri\Downloads\ocr\ocr\hs_err_pid4152.log
#

# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Info in fopenReadFromMemory: work-around: writing to a temp file

### Please provide steps to reproduce where possible

_No response_

### Expected Results

read my jpeg image

### Actual Results

bug

### What Java Version are you using?

java --version 17

### What is your operating system and platform?

window

### How did you install Java?

_No response_

### Did it work before?

_No response_

### Did you test with the latest update version?

_No response_

### Did you test with other Java versions?

_No response_

### Relevant log output

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the attached hs_err_pid4152.log and the reported problematic frame in libtesseract53.dll. Reproduce the JPEG read on Windows with Java 17, collecting the missing installation, Java-version, and reproduction details; done means obtaining a reliable reproduction or enough evidence to identify where the native crash should be reported.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.