# Client crash 7.9.0 **URL:** \ **Category:** Ignition\ **Created:** [October 19, 2016, 11:32pm UTC](https://forum.inductiveautomation.com/t/client-crash-7-9-0/12260 "2016-10-19T23:32:34Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![gekkoman](https://avatars.discourse-cdn.com/v4/letter/g/c89c15/32.png) [@gekkoman](https://forum.inductiveautomation.com/u/gekkoman)\ **Post date:** [October 19, 2016, 11:32pm UTC](https://forum.inductiveautomation.com/t/client-crash-7-9-0/12260/1 "2016-10-19T23:32:34Z")
Greetings, Am getting complete hang of client using global templates, including diagnostics. At time of crash code is producing no errors and resource utilisation etc is normal. Diagnostics hangs at same time. The template is still very much alpha so is quite crude. I have attached global template save and a sinle window project that uses the template. To reproduce fault…run the project in preview and simply mousover the menus. A megamenu popup shoudl appear when you mouseover the buttons. It all works fine for a while but at some point it just hangs…move your mouse repeatedly over the buttons and for me it crashes in under 30 seconds. ---
**Author:** ![gekkoman](https://avatars.discourse-cdn.com/v4/letter/g/c89c15/32.png) [@gekkoman](https://forum.inductiveautomation.com/u/gekkoman)\ **Post date:** [October 19, 2016, 11:38pm UTC](https://forum.inductiveautomation.com/t/client-crash-7-9-0/12260/2 "2016-10-19T23:38:39Z")
Looking more and more like a bug somewhere in the event execution system. I removed the diagnostic print statements from the code as these are typically slow operations…and lo and behold I cannot get it to crash anymore. Could a combination of mouse entered and exited events (eg exited event before completion of entered code for example) be causing a deadlock?? ---
**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\ **Post date:** [October 20, 2016, 1:57pm UTC](https://forum.inductiveautomation.com/t/client-crash-7-9-0/12260/3 "2016-10-20T13:57:37Z")
It’s going to be easiest to solve this if you call or email support… ---
**Author:** ![system](https://us1.discourse-cdn.com/inductiveautomation/original/2X/c/c985ea71ed53a8f212f3920ddf03fe05249170b8.png) [@system](https://forum.inductiveautomation.com/u/system)\ **Post date:** [November 22, 2016, 3:14am UTC](https://forum.inductiveautomation.com/t/client-crash-7-9-0/12260/4 "2016-11-22T03:14:05Z")
This crash is more prevasive than just the symptoms outlined above. To reproduce: Create two identical projects each containing one main window containing one button which executes ```auto system.util.retarget("") ``` Now run one of the project and start clicking buttons…it does not take long before the client crashes, can be in as little a 5-6 clicks. I am on linux, am running server on localhost so there will be no network issues. ---
**Author:** ![gekkoman](https://avatars.discourse-cdn.com/v4/letter/g/c89c15/32.png) [@gekkoman](https://forum.inductiveautomation.com/u/gekkoman)\ **Post date:** [November 22, 2016, 4:06am UTC](https://forum.inductiveautomation.com/t/client-crash-7-9-0/12260/5 "2016-11-22T04:06:19Z")
UPDATE: Issue only occurs when launching from designer eg Tools-\>Launch Project staged, or published. Running project directly (native or weblaunch) works as expected. Crashed process command via designer javaws -splash:/usr/share/icedtea-web/javaws\_splash.png -Xbootclasspath/a:/usr/share/icedtea-web/netx.jar:/usr/share/icedtea-web/plugin.jar:/usr/share/java/js.jar -Xms8m -Xms32M -Xmx256M -XX:MaxPermSize=128m -Xms32M -Xmx256M -XX:MaxPermSize=128m -Xms32M -Xmx256M -XX:MaxPermSize=128m -classpath /usr/lib/jvm/default-runtime/lib/rt.jar:/usr/lib/jvm/default-runtime/lib/jfxrt.jar -Dicedtea-web.bin.name=javaws -Dicedtea-web.bin.location=/usr/share/icedtea-web/bin/javaws net.sourceforge.jnlp.runtime.Boot -Xnofork [localhost:8088/main/system/launch/client/a.jnlp](http://localhost:8088/main/system/launch/client/a.jnlp) Non crashing command via web launch javaws -splash:/usr/share/icedtea-web/javaws\_splash.png -Xbootclasspath/a:/usr/share/icedtea-web/netx.jar:/usr/share/icedtea-web/plugin.jar:/usr/share/java/js.jar -Xms8m -Xms32M -Xmx256M -XX:MaxPermSize=128m -Xms32M -Xmx256M -XX:MaxPermSize=128m -Xms32M -Xmx256M -XX:MaxPermSize=128m -classpath /usr/lib/jvm/default-runtime/lib/rt.jar:/usr/lib/jvm/default-runtime/lib/jfxrt.jar -Dicedtea-web.bin.name=javaws -Dicedtea-web.bin.location=/usr/share/icedtea-web/bin/javaws net.sourceforge.jnlp.runtime.Boot -Xnofork /tmp/mozilla\_taro0/a-1.jnlp Only difference is the location to the jnlp. The jnlp are identical except for the launchts, so no issue here either. This leaves the designer being the culprit. This is in a way good news as it means the projects will not be crashing in production. Workaround for now is not to use the designer for launching during dev. ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [November 22, 2016, 7:00pm UTC](https://forum.inductiveautomation.com/t/client-crash-7-9-0/12260/6 "2016-11-22T19:00:39Z")
I've had issues with JavaWS on my Mac when I had, unbeknownst to me, a couple of different versions of java floating around. When I used the Native Client Launcher, I had no issues whatsoever. Later I found out the multiple java versions issue, resolved that, and haven't seen those client crashes return since. Might be worth a little inspection, just in case something similar to this is happening to you. ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [November 22, 2016, 10:30pm UTC](https://forum.inductiveautomation.com/t/client-crash-7-9-0/12260/7 "2016-11-22T22:30:19Z")
Recently came across this article, it might be helpful: [https://support.inductiveautomation.com/index.php?/Knowledgebase/Article/View/87/0/running-multiple-versions-of-java-on-the-same-windows-machine](https://support.inductiveautomation.com/index.php?/Knowledgebase/Article/View/87/0/running-multiple-versions-of-java-on-the-same-windows-machine) ---
**Author:** ![PerryAJ](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/perryaj/32/3281_2.png) [@PerryAJ](https://forum.inductiveautomation.com/u/PerryAJ)\ **Post date:** [November 28, 2016, 4:56pm UTC](https://forum.inductiveautomation.com/t/client-crash-7-9-0/12260/8 "2016-11-28T16:56:36Z")
In addition to what kcollins said, there are some bugs relating to OSX Accessibility API that may cause application crashes. I run a few 3rd party tools for documentation and key/mouse interaction, and have seen crashes in designer (and clients) sometimes as a result. Java desktop applications aren’t alone in these crashes, but it does seem to happen more often than with native programs. If in OSX/MacOS, go to System Preferences -\> Security & Privacy -\> Accessibility. Uncheck items in there and see if the crashing persists. In my case: BetterTouchTool, Hyperdock, Dash, Discord and Hipchat all seem to contribute to application crashes through accessibility features on occasion. Most people won’t have anything installed that use Accessibility features, and I don’t think I’ve ever seen a production system running on OSX, so this is mostly geared toward developers who may work on a mac. Get in touch with support if you continue to have issues, as we aren’t familiar with others seeing the particular problem you describe. ---
**Author:** ![gekkoman](https://avatars.discourse-cdn.com/v4/letter/g/c89c15/32.png) [@gekkoman](https://forum.inductiveautomation.com/u/gekkoman)\ **Post date:** [November 30, 2016, 6:23am UTC](https://forum.inductiveautomation.com/t/client-crash-7-9-0/12260/9 "2016-11-30T06:23:44Z")
The good news is that testing on windows box with single version of java appears to works as expected so it seems issue may be related to my system (arch linux) I’ll test on some other linux versions and see if the problem is related to my install or linux in general. Won’t be the first time Java does weird stuff (write once, debug everywhere 🙂) Related Details: taro@osiris ~ $ archlinux-java status Available Java environments: java-7-openjdk java-8-openjdk (default) taro@osiris /usr/lib $ env | grep -i ‘java|jvm’ PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/opt/opencascade/bin:/usr/bin/site\_perl:/usr/bin/vendor\_perl:/usr/bin/core\_perl:/usr/bin/ignition:/usr/bin/ignition taro@osiris /usr/lib $ ls -al jvm total 268 drwxr-xr-x 4 root root 4096 Feb 18 2016 . drwxr-xr-x 274 root root 258048 Nov 2 07:36 … lrwxrwxrwx 1 root root 14 Feb 18 2016 default -\> java-8-openjdk lrwxrwxrwx 1 root root 18 Feb 18 2016 default-runtime -\> java-8-openjdk/jre drwxr-xr-x 6 root root 4096 Feb 18 2016 java-7-openjdk drwxr-xr-x 6 root root 4096 Feb 18 2016 java-8-openjdk ---
**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\ **Post date:** [November 30, 2016, 3:04pm UTC](https://forum.inductiveautomation.com/t/client-crash-7-9-0/12260/10 "2016-11-30T15:04:42Z")
Could also be an openjdk issue. I’ve been much happier since I changed my standard Linux set up routine to wipe out everything openjdk related and install the official Oracle Java. YMMV.