JNA 5.13.0: C++ Side Mutex Creation Fails with "Invalid Memory" Error
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the Java JNA call to the MSVC-built C++ library using the provided createMutex example, then inspect the Java/native boundary and the mutex construction or locking point where invalid memory is reported. Done means identifying the cause of the invalid memory access and confirming a corrected interaction on Windows 10.
Written by the indexing model from the issue text.
Description
Description:
When using JNA 5.13.0 to interface with a C++ library, an issue arises where attempting to create a mutex on the C++ side results in an "invalid memory" error. This issue occurs consistently whenever the mutex creation is attempted. Below are the details of the environment and the problem:
Environment:
- Java Version: 1.8.0_361 (Oracle JDK)
- JNA Version: 5.13.0(5.17.0 same err)
- Operating System: [Windows 10]
- C++ Compiler/Environment: [MSVC]
Problem Description:
The Java application uses JNA to interact with a native C++ library.
On the C++ side, when attempting to create a std::mutex (or any other type of mutex), the program throws an error related to invalid memory access.
The error message or behavior indicates that the memory allocation or usage for the mutex is corrupted or invalid.
Example Code:
Java Side:
public interface MyLibrary extends Library {
MyLibrary INSTANCE = Native.load("mylibrary", MyLibrary.class);
void createMutex();
}
public class Main {
public static void main(String[] args) {
MyLibrary.INSTANCE.createMutex();
}
}
C++ Side:
#include <mutex>
extern "C" {
void createMutex() {
std::mutex mtx; // Attempting to create a mutex
mtx.lock(); // Error occurs here or during construction
mtx.unlock();
}
}
Error
java.lang.Error: Invalid memory access
- Dominant language
- Java
- Stars
- 8.9k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from java-native-access/jna
-
Incorrect mapping of c.s.j.platform.unix.solaris.LibKstat.KstatCtlPossibly taken @dbwiddis claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
java-native-access/jna#1740 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 66/100
java-native-access/jna#1738 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
java-native-access/jna#1736 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
java-native-access/jna#1717 ·
-
Windows32Exception - The parameter is incorrectPossibly taken @marktech0813 claimed this 331 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
java-native-access/jna#1700 · 11 comments ·
All issues in java-native-access/jna
Similar issues
-
backend
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bcgov/nr-forest-client#2524 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Sinytra/ForgifiedFabricAPI#298 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
team:Lumberjack
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
OpenLiberty/open-liberty#35998 ·
Maintainers usually reply within 1 day