# Memory Leakage / Garbage Collection Issue

**URL:** <https://forum.inductiveautomation.com/t/memory-leakage-garbage-collection-issue/27820>\
**Category:** Ignition\
**Created:** [August 27, 2019, 11:55pm UTC](https://forum.inductiveautomation.com/t/memory-leakage-garbage-collection-issue/27820 "2019-08-27T23:55:51Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![byrnep](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@byrnep](https://forum.inductiveautomation.com/u/byrnep)\
**Post date:** [August 28, 2019, 2:20pm UTC](https://forum.inductiveautomation.com/t/memory-leakage-garbage-collection-issue/27820/6 "2019-08-28T14:20:14Z")

</div>

Thanks, Phil.

Looks like Jmap is going to be a project with Windows, at least it was for this guy. Including as for posterity. FWIW, what he's describing is exactly what we're seeing, though no resolution is posted.

> [@Using jmap to diagnose heap related issues in Ignition?](http://forum.inductiveautomation.com/t/using-jmap-to-diagnose-heap-related-issues-in-ignition/25881/14):
>
> I went and looked at the suggested thread. Seems like an entire project just to get java utilities to run under windows. Thanks for the suggestion though. Haven’t gone down the patch of VisualVM. Not sure what it is and what is required to install it. The target system is in production and will not tolerate a restart so if a system restart is required I can’t go down that path. Another issue I might be encountering is that my JDK is not the identical version of the runtime environment version. …

---

_[View the full topic](https://forum.inductiveautomation.com/t/memory-leakage-garbage-collection-issue/27820)._