Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Crash with openj9 #79

Open
StefanSchmaltz opened this issue May 14, 2019 · 0 comments · May be fixed by #80
Open

Crash with openj9 #79

StefanSchmaltz opened this issue May 14, 2019 · 0 comments · May be fixed by #80

Comments

@StefanSchmaltz
Copy link

From: eclipse-openj9/openj9#5696

memory corruption detected
openj9 64bit jdk8u212-b03

Just calling the tutorial from
https://com4j.kohsuke.org/tutorial.html

java -jar tlbimp.jar -o wsh -p test.wsh %WINDIR%\system32\wshom.ocx

09:54:37.499 0x2e18500 omrport.359 * ** ASSERTION FAILED ** at ../../omr/port/common/omrmemtag.c:145: ((memoryCorruptionDetected))
JVMDUMP039I Speicherauszugsereignis "traceassert", Detail "" um 2019/05/09 11:54:37 - bitte warten.
JVMDUMP032I JVM forderte als Antwort auf ein Ereignis einen Speicherauszug von System mit "D:\Projekte\david\core.20190509.115437.118336.0001.dmp" an
JVMDUMP010I Speicherauszug von System in D:\Projekte\david\core.20190509.115437.118336.0001.dmp geschrieben
JVMDUMP032I JVM forderte als Antwort auf ein Ereignis einen Speicherauszug von Java mit "D:\Projekte\david\javacore.20190509.115437.118336.0002.txt" an
JVMDUMP010I Speicherauszug von Java in D:\Projekte\david\javacore.20190509.115437.118336.0002.txt geschrieben
JVMDUMP032I JVM forderte als Antwort auf ein Ereignis einen Speicherauszug von Snap mit "D:\Projekte\david\Snap.20190509.115437.118336.0003.trc" an

Does not happen with oracle vm

When executing above line:
javacore.20190509.115437.118336.0002.txt

When using com4j in our application:
javacore.20190509.120054.117232.0002.txt
DanHeidinga added a commit to DanHeidinga/com4j that referenced this issue May 14, 2019
@DanHeidinga
Correct buffer size to fix memory corruption
000a42a 
The analysis in eclipse-openj9/openj9#5696 shows that there
is a out of bounds access that is fixed by increasing
the buffer size by 8.  Validated by having the VM
increase all unsafe allocates by 8 and the problem
no longer occurs.

fixes: kohsuke#79

Signed-off-by: Dan Heidinga <daniel_heidinga@ca.ibm.com>
@DanHeidinga DanHeidinga linked a pull request May 14, 2019 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Correct buffer size to fix memory corruption DanHeidinga/com4j
1 participant
@StefanSchmaltz