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

Fatal error in JAVA Runtime #35

Closed
MDashK opened this issue Jul 25, 2016 · 7 comments
Closed

Fatal error in JAVA Runtime #35

MDashK opened this issue Jul 25, 2016 · 7 comments

Comments

@MDashK
Copy link

MDashK commented Jul 25, 2016

With this newest release, I get an error as soon as I try to catch a Pkmn:

A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000642f51eb, pid=5072, tid=0x0000000000001c28
JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build 1.8.0_102-b14)
Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode windows-amd64 compressed oops)
Problematic frame:
C [jfxwebkit.dll+0xd651eb]
Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
If you would like to submit a bug report, please visit:
http://bugreport.java.com/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.

I can post the rest of the log, if needed.

@MDashK MDashK changed the title Falat error in JAVA Runtime Fatal error in JAVA Runtime Jul 25, 2016
@null-dev
Copy link
Contributor

I don't think we can fix this (it's C++ code in the JavaFX library).

@MDashK
Copy link
Author

MDashK commented Jul 25, 2016

Well, all I can say is that this issue only happens to me in this latest 0.1.7 version. Not in the previous 0.1.6 version...

@SonnyX
Copy link

SonnyX commented Jul 25, 2016

Probably due to 449e347 (changed how paths were shown)
or less likely as I believe its already in 1.6: 53e1730

@SwipeX
Copy link
Owner

SwipeX commented Jul 25, 2016

Correct that it most likely has to do with the PolyLine[] drawing.

@MDashK
Copy link
Author

MDashK commented Jul 25, 2016

Yeah, when I looked at the changes from both versions, I also suspected it was related to the PolyLine change. So, what can I do to fix this? Any ideas?

@MDashK
Copy link
Author

MDashK commented Jul 25, 2016

As of version 0.1.8, this no longer happens to me. Seems to be fixed. Thanks! =D

@SwipeX
Copy link
Owner

SwipeX commented Jul 25, 2016

As far as I am aware, (I actually have gotten this a few times), this has not occurred for me in quite a while. I'll close this, but if it happens again, reopen this or at least reference it.

@SwipeX SwipeX closed this as completed Jul 25, 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

4 participants