# Using runScript, any effects on Heap Memory

**URL:** <https://forum.inductiveautomation.com/t/using-runscript-any-effects-on-heap-memory/36682>\
**Category:** Ignition\
**Created:** [July 14, 2020, 1:43pm UTC](https://forum.inductiveautomation.com/t/using-runscript-any-effects-on-heap-memory/36682 "2020-07-14T13:43:52Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [July 14, 2020, 5:09pm UTC](https://forum.inductiveautomation.com/t/using-runscript-any-effects-on-heap-memory/36682/6 "2020-07-14T17:09:27Z")

</div>

> [@bpreston](#):
>
> Support told me it was because it queried at a 250ms rate looking for new alarms but was slowed by the VPN connection causing it to not get a response before it fired again.

It wouldn't fire _again_ while the first one was still going, but it could very well fire again immediately after it finishes evaluating, effectively freezing your UI permanently.

---

_[View the full topic](https://forum.inductiveautomation.com/t/using-runscript-any-effects-on-heap-memory/36682)._