# Java crashing on clients after a few days. hs\_err\_pid inside **URL:** \ **Category:** Ignition\ **Created:** [May 10, 2014, 5:41pm UTC](https://forum.inductiveautomation.com/t/java-crashing-on-clients-after-a-few-days-hs-err-pid-inside/8433 "2014-05-10T17:41:26Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![framebuilder](https://avatars.discourse-cdn.com/v4/letter/f/96bed5/32.png) [@framebuilder](https://forum.inductiveautomation.com/u/framebuilder)\ **Post date:** [May 10, 2014, 5:41pm UTC](https://forum.inductiveautomation.com/t/java-crashing-on-clients-after-a-few-days-hs-err-pid-inside/8433/1 "2014-05-10T17:41:26Z")
We have a couple Ignition clients whose Java crashes randomly after 10-14 days, and I need some help debugging it. It never starts back up and the computer sits there with the Desktop showing. They are all the same hardware, same OS, same Project. Hardware: WYSE T50 thin client OS: Ubuntu 10.04 LTS CPU: 1GHz ARMv7 RAM: 1GB The Project is very simple–8 tag subscriptions, no SQL queries. Client Memory setting in Project: Min: 32MB Max: 256MB Gateway version: 7.6.4 (b2013112117) | 64-bit Gateway Java version: Oracle Corporation 1.7.0\_51 Windows 2008R2 VM Client Java version: Java™ SE Runtime Environment (build 1.7.0\_55-b13) Java HotSpot™ Client VM (build 24.55-b03, mixed mode) I’ve tried different versions of Oracle Java and they all exhibit the same behavior. I haven’t tried 1.8 yet, though. I’m thinking about writing a watchdog service and restarting Java if it crashes, but I’d really like to get to the root of this problem. The hs\_err\_pidXXXX.logs are attached. I can’t understand them and I hope you guys can. I’m hoping it’s something simple with a memory setting… Client1 [attachment=1]hs\_err\_pid1570.log[/attachment] Client2 [attachment=0]hs\_err\_pid1650.log[/attachment] ---
**Author:** ![james.hunt](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@james.hunt](https://forum.inductiveautomation.com/u/james.hunt)\ **Post date:** [May 12, 2014, 5:51pm UTC](https://forum.inductiveautomation.com/t/java-crashing-on-clients-after-a-few-days-hs-err-pid-inside/8433/2 "2014-05-12T17:51:55Z")
Are these thin clients connecting to a Terminal server or are you running the ignition application native on the Thin client itself? In regards to the lock-ups , if you are running the application native, the ARM 7 processor is going to give you problems. If you are wanting to troubleshoot this problem I would look at the wrapper.log files and see what the gateway is say about these lock-ups. ---
**Author:** ![framebuilder](https://avatars.discourse-cdn.com/v4/letter/f/96bed5/32.png) [@framebuilder](https://forum.inductiveautomation.com/u/framebuilder)\ **Post date:** [May 12, 2014, 7:58pm UTC](https://forum.inductiveautomation.com/t/java-crashing-on-clients-after-a-few-days-hs-err-pid-inside/8433/3 "2014-05-12T19:58:18Z")
The thin clients are running Java natively–ie, NOT connecting to any Terminal Servers, etc. Just to be clear, the clients aren’t locking up. Java is crashing while running the project. I’m having difficulties correlating the times that the clients crash. I ended up writing a watchdog service to verify the Java process is running. If it’s not, it starts it back up and writes to an error log with the date/time. Presumably, this will allow me to look at the wrapper.log file to correlate the issues but I’m not sure what level logging will show me anything useful…especially because I don’t think there is an issue with the Gateway. Which logger/level settings should I use? Does IA not support Oracle Java on ARMv7 ? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 12, 2014, 8:52pm UTC](https://forum.inductiveautomation.com/t/java-crashing-on-clients-after-a-few-days-hs-err-pid-inside/8433/4 "2014-05-12T20:52:14Z")
It’s as “supported” as it gets. It sounds like you’re just running into a bug in the JRE, maybe one that’s only present in the ARM version, or even on these ARM chips - who knows! There’s pretty much nothing we can do. We will submit the crash logs to Oracle and then just hope and pray. It’s certainly worth your time to see if Java 8 has already fixed this.