# Client CPU high

**URL:** <https://forum.inductiveautomation.com/t/client-cpu-high/39910>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [October 22, 2020, 9:50am UTC](https://forum.inductiveautomation.com/t/client-cpu-high/39910 "2020-10-22T09:50:58Z")\
**Posts on this page:** 11\
**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:** [October 22, 2020, 9:50am UTC](https://forum.inductiveautomation.com/t/client-cpu-high/39910/1 "2020-10-22T09:50:58Z")

</div>

ignition v7.9.9, the client pc : win10,16G  
when I open and close many pop windows, the client cpu become high, then I set the pop windows cache to never or auto or always, CPU usage remains the same, how do I find out why? At the same time, CPU usage and memory on the ignition’s server pc are normal.

---

<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:** [October 22, 2020, 10:20am UTC](https://forum.inductiveautomation.com/t/client-cpu-high/39910/2 "2020-10-22T10:20:32Z")

</div>

That usually means you’ve created an infinite loop in your events or circular reference in your bindings. Unfortunately, there’s so many possibilities that there isn’t any sure-fire way to nail it down. Start by watching CPU while opening each window to see if the problem starts with a particular window.

---

<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:** [October 22, 2020, 10:31am UTC](https://forum.inductiveautomation.com/t/client-cpu-high/39910/3 "2020-10-22T10:31:16Z")

</div>

when I close the pop window, the infinite loop in my events or circular reference can end?

---

<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:** [October 22, 2020, 11:49am UTC](https://forum.inductiveautomation.com/t/client-cpu-high/39910/4 "2020-10-22T11:49:18Z")

</div>

Not necessarily. Open them one at a time. If it starts with the popup window, then you need to investigate that window.

---

<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:** [October 22, 2020, 12:04pm UTC](https://forum.inductiveautomation.com/t/client-cpu-high/39910/5 "2020-10-22T12:04:34Z")

</div>

when I turning on and off the same popup windows over and over again, about 20 times, can increase CPU utilization to 60%. these popup windows use propety changes events, there are some operations to query the database(sql server), but the amount of data being queried is very small

---

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [October 22, 2020, 12:25pm UTC](https://forum.inductiveautomation.com/t/client-cpu-high/39910/6 "2020-10-22T12:25:11Z")

</div>

Do you have tab strips in your popups?

---

<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:** [October 22, 2020, 12:32pm UTC](https://forum.inductiveautomation.com/t/client-cpu-high/39910/7 "2020-10-22T12:32:27Z")

</div>

No，has butten, chart, numeric text fieid, alarm status table

---

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [October 22, 2020, 1:08pm UTC](https://forum.inductiveautomation.com/t/client-cpu-high/39910/8 "2020-10-22T13:08:20Z")

</div>

Ok, I asked because a tab strip with cell bindings have been known to cause problems.

Any scripting? Has this always happened, or just recently? If just recently, what’s changed?

---

<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:** [October 22, 2020, 1:14pm UTC](https://forum.inductiveautomation.com/t/client-cpu-high/39910/9 "2020-10-22T13:14:27Z")

</div>

always

---

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [October 22, 2020, 1:30pm UTC](https://forum.inductiveautomation.com/t/client-cpu-high/39910/10 "2020-10-22T13:30:07Z")

</div>

Maybe an easy way to troubleshoot is to selectively remove components until it stops, to isolate which component(s) is causing the problem. I would also call IA support and get them involved.

---

<div class="post-metadata">

**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:** [October 22, 2020, 1:32pm UTC](https://forum.inductiveautomation.com/t/client-cpu-high/39910/11 "2020-10-22T13:32:12Z")

</div>

It might help to install JDK 8 or 9 on that client, depending what you are running it with now, and then use the `jps` tool to get the pid of the client and then `jstack` to capture a few thread dumps while the CPU usage is high. Maybe we can see something there.
