What are possible reasons for memory consumption going up on stack that isn't doing much?
bobsneidar at iotecdigital.com
Mon Jul 9 17:04:42 CEST 2018
It may help to put a wait x milliseconds with messages in the repeat loop. This will give the engine a chance to do housecleaning.
> On Jul 7, 2018, at 16:15 , Tom Glod via use-livecode <use-livecode at lists.runrev.com> wrote:
> Hi folks,
> I have a stack that has 2 or 3 self perpetuating messages which do a few
> checks and the like....they run every 250 milliseconds or so.
> There is no input data into the program unless I specifically send it there.
> but while my program is sitting there ....repeating its loops and checks
> for incoming input ...... the memory consumption is steadily going up by .1
> megabytes at a time.
> I have watched my global variables , there is nothing being added to them
> and most handlers have local variables that clear out when the handler
> This happens in IDE and standalone.
> This app is made to stay in memory so this is not acceptable, because after
> 2 days it will get up to 2gb or whatever....so i cannot let this remain.
> maybe if i let it sit there it will eventually clear out ..but i haven't
> seen that happen yet.
> I just don't know where to look. maybe i just found a memory leak
> ....Thanks for any input
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode