# Clock Drift Issue Garbage Collection Issue Gateway Restarts Automatically

**URL:** <https://forum.inductiveautomation.com/t/clock-drift-issue-garbage-collection-issue-gateway-restarts-automatically/61629>\
**Category:** Ignition\
**Created:** [July 7, 2022, 1:28pm UTC](https://forum.inductiveautomation.com/t/clock-drift-issue-garbage-collection-issue-gateway-restarts-automatically/61629 "2022-07-07T13:28:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [July 7, 2022, 1:40pm UTC](https://forum.inductiveautomation.com/t/clock-drift-issue-garbage-collection-issue-gateway-restarts-automatically/61629/2 "2022-07-07T13:40:23Z")

</div>

It seems you are not alone.

> [@Ignition Gateway restarts Itself (v8.1.18 16GB Memory allocation)](https://forum.inductiveautomation.com/t/ignition-gateway-restarts-itself-v8-1-18-16gb-memory-allocation/61598):
>
> Yesterday we concurrently updated the gateway memory allocation (8GB to 16GB) and updated the ignition software version (v8.1.17 to v 8.1.18). Today we have had a number of instances where the gateway appear to have restarted itself, preceded by ClockDriftDetector and Timeout warnings. My first thought was to look at garbage collection due to things I had read in the past but I understand that Ignition now uses the recommended G1C1 garbage collector by default. We are investigating further b…

---

_[View the full topic](https://forum.inductiveautomation.com/t/clock-drift-issue-garbage-collection-issue-gateway-restarts-automatically/61629)._
