tduva
commented
7 years ago Do you have the Java Crash Log?
Open kmslogic opened 7 years ago
tduva
commented
7 years ago Do you have the Java Crash Log?
kmslogic
commented
7 years ago How can I get it?
On Fri, Nov 10, 2017 at 12:59 PM tduva notifications@github.com wrote:
Do you have the Java Crash Log?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/chatty/chatty/issues/202#issuecomment-343571234, or mute the thread https://github.com/notifications/unsubscribe-auth/ABrxXReskJiHa-vWyPZN33YgqTh8WY21ks5s1KsIgaJpZM4QaA1r .
-- Sent from Gmail Mobile
tduva
commented
7 years ago It should be a file called hs_err_pid[numbers].log. It might be in the folder where you start Chatty, or whatever your working directory is. Or if it can't write to that maybe the system's temp folder. You can try to set where it is written to with the Java launch parameter: -XX:ErrorFile=C:/hs_err_pid%p.log (I'm not sure if it actually works like that since I never could test it with a crash).
See: https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/felog001.html
tduva
commented
7 years ago It might also work to start Chatty from the commandline, which in this case might reveal output from the JVM when Chatty already closed.
tduva
commented
7 years ago Writing it to C:/ didn't work for me, but writing it to another drive worked. Although starting Chatty from the commandline should tell you where it saved it either way, if the crash works the same as the forced one I'm testing with.
kmslogic
commented
7 years ago Ok, I had no luck writing the error log. I did capture the output from running it from the command line but nothing jumped out at me.
This is the command line I was using (tried a few variations of the -xx:ErrorFile with forward slashes, drives, etc but no joy). file didn't exist in the file chatty runs from or in the temp folder
In terms of output I don't see any mention of the crash happening.
java -XX:ErrorFile=Chatty.Log -jar chatty.jar >output.txt 2>&1
This is the error in the event log so it looks like it's having a problem with intellitype
Faulting application name: javaw.exe, version: 9.0.0.0, time stamp: 0x5982a7aa Faulting module name: JIntellitype.dll, version: 0.0.0.0, time stamp: 0x4b5c9033 Exception code: 0xc0000005 Fault offset: 0x0000000000001976 Faulting process id: 0x4794 Faulting application start time: 0x01d35a5b6a200dac Faulting application path: C:\Program Files\Java\jre-9\bin\javaw.exe Faulting module path: D:\Users\Kelly\Desktop\Chatty_0.9b1_hotkey_64bit\JIntellitype.dll Report Id: e4b6b2ce-b90e-4997-9cdc-3b365c4d12ca Faulting package full name: Faulting package-relative application ID:
On Fri, Nov 10, 2017 at 2:02 PM, tduva notifications@github.com wrote:
Writing it to C:/ didn't work for me, but writing it to another drive worked. Although starting Chatty from the commandline should tell you where it saved it either way, if the crash works the same as the forced one I'm testing with.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/chatty/chatty/issues/202#issuecomment-343584957, or mute the thread https://github.com/notifications/unsubscribe-auth/ABrxXVbu5idIDGR0hRFke8a1icFKMDexks5s1LnzgaJpZM4QaA1r .
[2017-11-10 14:38:14 INFO] ### Log start (2017-11-10 14:38:14 -0700) [chatty.TwitchClient/
tduva
commented
7 years ago Nothing related to the JIntellitype.dll has changed between v0.8.7 and v0.9b1. Have you updated Java recently or changed anything else?
Maybe you could try the Standalone version.
tduva
commented
7 years ago Just to clarify, the "Event log" you got the error from is the Windows Event log?
kmslogic
commented
7 years ago Yes
On Fri, Nov 10, 2017 at 4:13 PM, tduva notifications@github.com wrote:
Just to clarify, the "Event log" is the Windows Event log?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/chatty/chatty/issues/202#issuecomment-343611486, or mute the thread https://github.com/notifications/unsubscribe-auth/ABrxXZOLw3NBUZa6UMyDtzSgezZtoe4Zks5s1NiEgaJpZM4QaA1r .
kmslogic
commented
7 years ago FWIW I tried beta 2 and it also crashes using the 64bit hotkey version. The vanilla version of beta1 and 2 work fine.
tduva
commented
7 years ago Vanilla version? You mean without the JIntellitype?
kmslogic
commented
7 years ago yes, that's what I mean
On Wed, Nov 15, 2017 at 12:38 PM, tduva notifications@github.com wrote:
Vanilla version? You mean without the JIntellitype?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/chatty/chatty/issues/202#issuecomment-344704638, or mute the thread https://github.com/notifications/unsubscribe-auth/ABrxXYAXp4aPtx2B9Nx7CzTVMSsr69vHks5s2z2rgaJpZM4QaA1r .
spacerecycler
commented
7 years ago For me, this only happens when I let Chatty launch with Java 9.0.1. If I launch it with Java 1.8.0_152 it works just fine. From the error above it looks like it might be an issue with Java 9.0.0 as well from reading the "Faulting application path".
kmslogic
commented
7 years ago can confirm this is with java 9.0.1
On Fri, Nov 17, 2017 at 10:44 AM, spacerecycler notifications@github.com wrote:
For me, this only happens when I let Chatty launch with Java 9.0.1. If I launch it with Java 1.8.0_152 it works just fine. From the error above it looks like it might be an issue with Java 9.0.0 as well from reading the "Faulting application path".
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/chatty/chatty/issues/202#issuecomment-345313416, or mute the thread https://github.com/notifications/unsubscribe-auth/ABrxXTVPiacIbisPAOkJ-Z3KOxt6jwQaks5s3cYIgaJpZM4QaA1r .
This error happens 100% of the time on exit. Is there additional information I can attach, or some setting I can try to change? This did not happen with the release version.