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.

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

Java VM crashes using mutliple instances on 64-bit environment #29

Open
patsimm opened this issue Feb 22, 2016 · 0 comments
Open

Java VM crashes using mutliple instances on 64-bit environment #29

patsimm opened this issue Feb 22, 2016 · 0 comments

Comments

@patsimm
Copy link

patsimm commented Feb 22, 2016

Hello,

I don't know if this is the fault of pty4j or the underlying winpty or even my own. So I have a java application that opens multiple terminals using JediTerm. When I open the second Terminal on a 64-bit Java environment I get the following error:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000776e32d0, pid=2076, tid=4092
#
# JRE version: 7.0_13-b20
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C  [ntdll.dll+0x532d0]  RtlFreeHeap+0xd0
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\...\hs_err_pid2076.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

This happens on every 64-bit java version as far as I have seen. When I use a 32-bit java version every thing works as expected.

I also got the following exception thrown:

Exception in thread "AWT-EventQueue-0" java.lang.Error: Invalid memory access
        at com.sun.jna.Native.invokeInt(Native Method)
        at com.sun.jna.Function.invoke(Function.java:383)
        at com.sun.jna.Function.invoke(Function.java:315)
        at com.sun.jna.Library$Handler.invoke(Library.java:212)
        at com.pty4j.windows.$Proxy1.winpty_start_process(Unknown Source)
        at com.pty4j.windows.WinPty.<init>(WinPty.java:45)
        at com.pty4j.windows.WinPtyProcess.<init>(WinPtyProcess.java:37)
        at com.pty4j.PtyProcess.exec(PtyProcess.java:77)
        at com.pty4j.PtyProcess.exec(PtyProcess.java:50)

Edit: I tested this behaviour now by just starting the class PtyMain from jediterm which reproduces the issue.

@patsimm patsimm closed this as completed Feb 23, 2016
@patsimm patsimm reopened this Feb 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant