Photoshop stops execution of scripts after certain amount of time

Question

We developed some scripts for importing and exporting certain parts of psd-files. The scripts are working perfectly, when executed directly via Run/Script.
But after implementing them within an extension in Configurator we figured out a kind of timeout after approximately 5 Minutes runtime.
So every script installed within an extension and run via the according palette will freeze Photoshop after this time.
If you run the script separately everything works, also longer than 5 Minutes.
Is there any javascript function to change the "timeout" in Photoshop?
This problem occurs on Mac, PC, CS5.5 and CC, on different computers.
Thanks in advance
Peter

Answer 1

Yes this is great thank you so much... I was searching for where to find that code I see I could have maybe used the listener browsing to the script perhaps... but also I might have to try and combine a few things.     This link here talks about a global assetspath _Adobe.assetsPath   in the configurator 4 for invoking javascript... and http://forums.adobe.com/thread/1244470   And this link here http://forums.adobe.com/thread/1016919m is talking about a global varailbe assetsPath .   I have to figure out how to have the scripts called from wherever the assets path gets installed right?   Lots of the .jsx files will end up in a folder after the .zxp installs... but I'm using Configurator 3 to get around the 4 issues with CC... I can still export and have functional CS6 and CC extensions this way out of Configurator 3 --- just loading the .ZXPs in Extension Manager CC - they work in Photoshop CC just fine.    This avoids the problems with the signatures people are having.     This timeout solution solves another major issue.  
Do I simply replace this "desc3241.putPath( idjsCt, new File( "/Applications/Adobe Photoshop CS5.1/Scripting/Sample Scripts/JavaScript/ActiveLayer.jsx" ) );"
with
"desc3241.putPath( idjsCt, new File( "/Applications/Adobe Photoshop CS5.1/Scripting/Sample Scripts/JavaScript/ActiveLayer.jsx" ) );"
I think my issue will be just trying to get the code going to the right folder and I might have to make two separate versions one for CS6 and one for CC -- because otherwise the code is the same in the script buttons... have to change all the buttons I wish there was a quick way to switch them to script instead of script file.   Just need them to run this code now, but make it go to either:
Adobe/CS6ServiceManager/Extensions/["MyExtensionName"]/content/["MyExtensionName".assets]/    -- in the case of a CS6 version,
And
Adobe/CEPServiceManager4/extensions/com.["MyExtensionCo.MyExtensionName"]/content/Configur ator-Panel.assets
From what I can see there must be a smart way to have it work, but maybe not universally for CS6 and CC extension... the way I am exporting my panel with the script-file buttons... it works when you install the same .zxp to extension manager cs6 or cc... but I'm sure with this time-out solution that might not work.   Still just using different code for two different saved versions in Configurator 3, I will export a CS6 .zxp and a CC one.     I'm still not ready to switch to using Configurator 4, I can't get my extensions to export where they install ok with the self-signed certificate, it never gets past the loading with Configurator 4 .zxp files it fails to authenticate or let the user bypass.  
Thanks for your help so much this is great progress!