Script running box becomes uncheck?

Hi all,
I could not find any posting on this verison of finding the running box uncheck. I got a greeter prim that avatars collide with when they tp onto my land. It databases about 500 names and give a dialog box greeting, a lm to new visitors to my shop and an IM to the visitor the next day with a thank you for visiting. The prim is transparent and phantomed. The prim contains 6 scripts. a main communicator script, five database scripts and a thank you script. The problem is that I find that one of the scripts runnig box has been uncheck a few time now. not the same script each time. Has anybody else experienced this with a non vehecle and non attachment? and / or can anyone explain why this is happeing? and / or can anyone tell me how to prevent the it from happening again?

Apex

A stack-heap collision will unceremoniously set the script to not running. You might want to do some scale testing with llGetFreeMemory() -- although it's not very reliable. With 500 names, though, unless you're dividing up those names into multiple "memory" scripts, that's a very likely cause of overrunning the 16Kb ceiling--though why it should happen in a different script on subsequent runs is a bit mysterious.

Hi Qie,
Thanks for repling. The 5 database scripts 'record' about 100 names each and I use mem check to flip the script to a non record state when free memory hits 300. Can stack heap uncheck a box and nots crash the script? When I check the box the script starts up without needing to be reset and goes on operating like nothing was wrong. So far it's not the "recording' database that gets turned off, but one of the other 5 scripts.

on a side note: I am still getting a crash on the recording script some times. How inaccurate is memcheck? My observations indicate a variation of about 100. Thats why I set my switch to 300 for extra safety. Do you think I need to find another type of switch to avoid the crash or just a higher safety margin?

Apex -- My apologies: I sure thought I'd seen it happen, but now I can't get the Running box to uncheck when a script hits stack-heap collision, nor with a math error, and indeed a Reset is necessary to get the script out of the run-time error condition. So the mystery is exactly as you originally stated it: What will turn off a script, other than a script explicitly turning it off? -- Qie