# Loading app scripts on a client

**URL:** <https://forum.inductiveautomation.com/t/loading-app-scripts-on-a-client/6812>\
**Category:** Ignition\
**Created:** [July 3, 2013, 10:57am UTC](https://forum.inductiveautomation.com/t/loading-app-scripts-on-a-client/6812 "2013-07-03T10:57:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![systemparadox](https://avatars.discourse-cdn.com/v4/letter/s/b5e925/32.png) [@systemparadox](https://forum.inductiveautomation.com/u/systemparadox)\
**Post date:** [July 3, 2013, 10:57am UTC](https://forum.inductiveautomation.com/t/loading-app-scripts-on-a-client/6812/1 "2013-07-03T10:57:58Z")

</div>

Hi. We’re currently investigating some scripting errors that are occurring with clients on slow connections.

We have quite a large collection of app scripts and some imports pull in quite a lot of code at once. I was hoping that someone could clarify how Ignition clients load the app scripts.

In the SDK, app is a single resource so from this I would believe that clients should download the entire app repository in one go and then load them on-demand from there. However, one of the issues seems to be that running a large script fails for whatever unknown reason, but then in the exception catch the client also fails to import our error handler function. This does seem a bit strange.

Is app transferred all at once or on a per-file basis?

Thanks.

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [August 14, 2013, 3:47am UTC](https://forum.inductiveautomation.com/t/loading-app-scripts-on-a-client/6812/2 "2013-08-14T03:47:17Z")

</div>

It is transferred all at once as you suspected, so I don’t think connection speed could come into play. It sounds like these clients may be running out of memory, maybe Perm-gen space. Can you disable your error handler and see if an error like that bubbles up?
