# Client PC CPU High

**URL:** <https://forum.inductiveautomation.com/t/client-pc-cpu-high/31235>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [January 11, 2020, 3:45pm UTC](https://forum.inductiveautomation.com/t/client-pc-cpu-high/31235 "2020-01-11T15:45:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![lyhkch](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lyhkch/32/9381_2.png) [@lyhkch](https://forum.inductiveautomation.com/u/lyhkch)\
**Post date:** [January 11, 2020, 3:45pm UTC](https://forum.inductiveautomation.com/t/client-pc-cpu-high/31235/1 "2020-01-11T15:45:40Z")

</div>

Hi, my server PC: windows server 2016 , 64G , Igniton v7.9.9 , jre-8u-181, SQL Server 2012  
client PC : windows 7, 16G, jre-8u-181 . JAVA : G1GC  
Sometimes, on the client computer, all the data becomes red color, the mouse click screen has no reflection, This happened yesterday morning。

 ![123](https://us1.discourse-cdn.com/inductiveautomation/original/2X/e/eda5ee53bad6ecd996d1ae624b0ef1c695c66189.png)  
[thread\_dump.txt](https://us1.discourse-cdn.com/inductiveautomation/original/2X/a/ac678a8e418cac9f3595c2955d55993d5e092000.txt) (77.2 KB)  
 ![4](https://us1.discourse-cdn.com/inductiveautomation/original/2X/3/368a771ce4a86f10d85b700a695590484298ca71.jpeg)

The red part of this picture is the time period when the error occurred。

 ![296269859](https://us1.discourse-cdn.com/inductiveautomation/original/2X/b/b94465d27fb37324880c763f454993251ff14352.jpeg)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [January 11, 2020, 4:47pm UTC](https://forum.inductiveautomation.com/t/client-pc-cpu-high/31235/2 "2020-01-11T16:47:53Z")

</div>

That usually means there’s an infinite loop buried in your client scripting somewhere (can be recursion with bindings instead of explicit) or a sleep() operation in the foreground. The foreground hangup can eventually break the gateway connection. When (if) it recovers, the connection is re-created, as shown in your gateway logs.

---

<div class="post-metadata">

**Author:** ![lyhkch](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lyhkch/32/9381_2.png) [@lyhkch](https://forum.inductiveautomation.com/u/lyhkch)\
**Post date:** [January 12, 2020, 12:08pm UTC](https://forum.inductiveautomation.com/t/client-pc-cpu-high/31235/3 "2020-01-12T12:08:02Z")

</div>

Thank you. There are some tag change events, and gateway timer scripts. How to know from the gateway log file

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [January 12, 2020, 1:51pm UTC](https://forum.inductiveautomation.com/t/client-pc-cpu-high/31235/4 "2020-01-12T13:51:09Z")

</div>

You can’t tell from the gateway log file. High Client CPU from these sorts of problems can only be debugged at the client (or in the designer). First, look for any windows or operator actions that are prone to triggering the broken UI. Instrument the scripting on those windows first.