# \[IGN-8636\]Cpu trend frozen **URL:** \ **Category:** Ignition\ **Created:** [August 23, 2022, 1:07pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324 "2022-08-23T13:07:59Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Federico\_Bustamante](https://avatars.discourse-cdn.com/v4/letter/f/59ef9b/32.png) [@Federico\_Bustamante](https://forum.inductiveautomation.com/u/Federico_Bustamante)\ **Post date:** [August 23, 2022, 1:08pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/1 "2022-08-23T13:08:00Z")
![cpu trend frozen](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/d/8d16097e5101be883d737681acfc8a9e672f354f.png) Does anyone have the same problem? ---
**Author:** ![Paul\_Verbovshchuk](https://avatars.discourse-cdn.com/v4/letter/p/f0a364/32.png) [@Paul\_Verbovshchuk](https://forum.inductiveautomation.com/u/Paul_Verbovshchuk)\ **Post date:** [August 23, 2022, 9:36pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/2 "2022-08-23T21:36:30Z")
I haven’t personally encountered this issue before. Are you historizing your gateway CPU usage tag? Located at [System]Gateway/Performance/CPU Usage. If so, does it’s trend match what you see on the gateway status? ---
**Author:** ![Federico\_Bustamante](https://avatars.discourse-cdn.com/v4/letter/f/59ef9b/32.png) [@Federico\_Bustamante](https://forum.inductiveautomation.com/u/Federico_Bustamante)\ **Post date:** [August 24, 2022, 11:27am UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/3 "2022-08-24T11:27:14Z")
Yes, it’s the same value there and It doesn’t change, but should. I still can’t find the issue ---
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [August 24, 2022, 12:37pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/4 "2022-08-24T12:37:19Z")
For an issue like this, I think it’s always best to reach out to support so they can look for themselves. Otherwise, I’m sure a gateway restart will do the trick. ---
**Author:** ![Federico\_Bustamante](https://avatars.discourse-cdn.com/v4/letter/f/59ef9b/32.png) [@Federico\_Bustamante](https://forum.inductiveautomation.com/u/Federico_Bustamante)\ **Post date:** [August 29, 2022, 5:42pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/5 "2022-08-29T17:42:16Z")
Hello guys, I update the version to 8.1.20. The frozen was solved and in another case the “-100” in cpu too thanks ! ---
**Author:** ![tprice](https://avatars.discourse-cdn.com/v4/letter/t/838e76/32.png) [@tprice](https://forum.inductiveautomation.com/u/tprice)\ **Post date:** [January 23, 2023, 6:33pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/6 "2023-01-23T18:33:10Z")
I am currently at 8.1.23 and I am having the same issue with the cpu freezing or flatlining. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/4/54486d1f195b18e025746eece3a57a29bf4ed583.png) ---
**Author:** ![Federico\_Bustamante](https://avatars.discourse-cdn.com/v4/letter/f/59ef9b/32.png) [@Federico\_Bustamante](https://forum.inductiveautomation.com/u/Federico_Bustamante)\ **Post date:** [January 23, 2023, 6:47pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/7 "2023-01-23T18:47:06Z")
Have you tried restarting gateway? (service) ---
**Author:** ![tprice](https://avatars.discourse-cdn.com/v4/letter/t/838e76/32.png) [@tprice](https://forum.inductiveautomation.com/u/tprice)\ **Post date:** [January 23, 2023, 6:50pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/8 "2023-01-23T18:50:05Z")
So, yes I have and that fixes it but, 3 or 4 weeks from now it will happen again. ---
**Author:** ![Steven\_Lee](https://avatars.discourse-cdn.com/v4/letter/s/fbc32d/32.png) [@Steven\_Lee](https://forum.inductiveautomation.com/u/Steven_Lee)\ **Post date:** [November 10, 2023, 4:30am UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/9 "2023-11-10T04:30:31Z")
I have the same problem. After reset gateway, a month later the CPU trend frozen. Everything seems to run OK. The CPU cannot be constant as the garbage collector is still working up and down, should the CPU also? Looks like is ignition problem after accumulating 1 months of data. ---
**Author:** ![jstrasser](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@jstrasser](https://forum.inductiveautomation.com/u/jstrasser)\ **Post date:** [April 23, 2024, 3:05pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/10 "2024-04-23T15:05:54Z")
We are on 8.1.37 and still have the exact same problem. Everything seems to be working normal but the CPU trend freezes about a month after restarting the gateway. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [April 23, 2024, 3:34pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/11 "2024-04-23T15:34:53Z")
@here, we're tracking this internally as ticket IGN-8636, but be aware that this is an "upstream" bug in Java itself. So far, we've only noticed the issue occur on Windows hosts, and _primarily_ in virtualized environments. Anyone running into this issue is encouraged to contact our [Support team](https://support.inductiveautomation.com/hc/en-us), ideally with the following information at hand: 1. OS type/version? 2. VM software and version? 3. Microsoft Hyper-V Version (if applicable)? We've got an active ticket with our Java vendor, but the more information we can provide them (and the more reports we have of this occurring), the better. ---
**Author:** ![Ryan\_Heintzleman](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@Ryan\_Heintzleman](https://forum.inductiveautomation.com/u/Ryan_Heintzleman)\ **Post date:** [October 1, 2024, 6:19pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/12 "2024-10-01T18:19:26Z")
When that CPU usage gets 'locked' at a certain rate (like 0.8%), is it actually limiting its usage, or is it just not updating (but still using more in the background)? We have a few ignition servers that keep hitting this issue recently. We have a perceived "slowdown" / timing delays when it occurs, but also this morning we had an issue where a specific application wasn't executing tag change scripts while that occurred (may or may not be related, but error logs didn't say anything). ---
**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:** [October 1, 2024, 8:16pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/13 "2024-10-01T20:16:50Z")
> [@Ryan\_Heintzleman](#): > > When that CPU usage gets 'locked' at a certain rate (like 0.8%), is it actually limiting its usage, or is it just not updating (but still using more in the background)? There isn't actually any limiting of CPU usage in this scenario--rather, the inquiry that Ignition does to the JVM to show the usage % (which then calls into native code to retrieve the information from the OS) is not behaving properly. ---
**Author:** ![Shawn\_Rieger1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/shawn_rieger1/32/57040_2.png) [@Shawn\_Rieger1](https://forum.inductiveautomation.com/u/Shawn_Rieger1)\ **Post date:** [December 16, 2025, 6:40pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/14 "2025-12-16T18:40:08Z")
Been a year hoping to see this resolved. Still having the issue on 8.1.44. Any update on this? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/6/76ebe3928e81758b511e7493f34f51794bc426e4.png) ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 16, 2025, 6:44pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/15 "2025-12-16T18:44:12Z")
We tracked the fix down to an issue with our JDK vendor. When we update the bundled Java version (8.1.51/8.3.3) this should be resolved. ---
**Author:** ![Dmitrii\_Lysenkov](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dmitrii_lysenkov/32/53728_2.png) [@Dmitrii\_Lysenkov](https://forum.inductiveautomation.com/u/Dmitrii_Lysenkov)\ **Post date:** [January 22, 2026, 2:46pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/16 "2026-01-22T14:46:27Z")
![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/3/83e65690b41b8a383fc679f1da1b4cae37641af2.png)Hi all, has anyone found a real solution to this issue with frozen CPU trends? We are running Ignition 8.1.43 and the trend is still freezing. ---
**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:** [January 22, 2026, 2:53pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/17 "2026-01-22T14:53:27Z")
> [@Dmitrii\_Lysenkov](#): > > We are running Ignition 8.1.43 > [@paul-griffith](#): > > When we update the bundled Java version (8.1.51/8.3.3) this should be resolved. Tried this yet? ---
**Author:** ![Dmitrii\_Lysenkov](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dmitrii_lysenkov/32/53728_2.png) [@Dmitrii\_Lysenkov](https://forum.inductiveautomation.com/u/Dmitrii_Lysenkov)\ **Post date:** [January 22, 2026, 5:17pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/18 "2026-01-22T17:17:59Z")
Hi Kevin, I’m a bit confused about this solution. My Ignition gateway shows Java version 17.0.11. Is there any other Java component that needs to be updated? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/7/f73096b5f10d98b2d77dc17475ae1c9a50172432.png) ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 22, 2026, 5:21pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/19 "2026-01-22T17:21:45Z")
Ignition has bundled a Java runtime since the release of 8.0.0. This bundled Java runtime gets upgraded periodically as Ignition updates. The latest patch release of Java 17 (17.0.12) is bundled automatically with Ignition versions 8.1.51 and 8.3.3. You're on an older version of Ignition, and therefore an older version of Java, and therefore known to be subject to the bug that is the topic of this thread. ---
**Author:** ![Dmitrii\_Lysenkov](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dmitrii_lysenkov/32/53728_2.png) [@Dmitrii\_Lysenkov](https://forum.inductiveautomation.com/u/Dmitrii_Lysenkov)\ **Post date:** [January 22, 2026, 5:26pm UTC](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324/20 "2026-01-22T17:26:38Z")
Got it, thanks for the clarification. So the recommendation is to upgrade Ignition itself, since the Java runtime is bundled. We’re currently running Ignition 8.1.43. [Next page](https://forum.inductiveautomation.com/t/ign-8636-cpu-trend-frozen/63324.md?page=2)