# Java.exe memory usage on PC startup

**URL:** <https://forum.inductiveautomation.com/t/java-exe-memory-usage-on-pc-startup/8676>\
**Category:** Ignition\
**Created:** [July 7, 2014, 8:15pm UTC](https://forum.inductiveautomation.com/t/java-exe-memory-usage-on-pc-startup/8676 "2014-07-07T20:15:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![RPostWVU](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@RPostWVU](https://forum.inductiveautomation.com/u/RPostWVU)\
**Post date:** [July 7, 2014, 8:15pm UTC](https://forum.inductiveautomation.com/t/java-exe-memory-usage-on-pc-startup/8676/1 "2014-07-07T20:15:31Z")

</div>

I’m noticing my PC reboot time has become excessive since installing which is what led me to realize the excessive amount of memory being consumed by Java.exe

If I reboot my pc and do nothing. I’m not actively using Ignition (and as this my my development machine I seldom use Igition). Java starts up and slowly creeps up to 1.1GB of my 4GB available ram and 25% of my i5 processor for about 5min.

I’d rather Ignition not come on at all automatically, just when I want to run it.

---

<div class="post-metadata">

**Author:** ![adamaustin](https://avatars.discourse-cdn.com/v4/letter/a/5f8ce5/32.png) [@adamaustin](https://forum.inductiveautomation.com/u/adamaustin)\
**Post date:** [July 8, 2014, 12:45pm UTC](https://forum.inductiveautomation.com/t/java-exe-memory-usage-on-pc-startup/8676/2 "2014-07-08T12:45:03Z")

</div>

Try changing your windows service, as per my response to [this thread](https://inductiveautomation.com/forum/viewtopic.php?f=70&t=11788).

---

<div class="post-metadata">

**Author:** ![RPostWVU](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@RPostWVU](https://forum.inductiveautomation.com/u/RPostWVU)\
**Post date:** [July 8, 2014, 10:57pm UTC](https://forum.inductiveautomation.com/t/java-exe-memory-usage-on-pc-startup/8676/3 "2014-07-08T22:57:14Z")

</div>

I checked Sevices.msc prior to posting, but apparently overlooked “Ignition Gateway”. Setting that service to manual did resolve it.
