Do we have a ballpark idea of what "large" might be? Is it more like a gigabyte or a few hundred megabytes or...? I know it will be variable and depend on other factors, but it would be nice to have a general idea.

On 9/26/19 11:12 PM, Dar Scott Consulting via use-livecode wrote:
I don't think that is large. If you are processing data the same size and 
somehow leaving the previous data around, that might build up. That might build 
up in queues and stacks, in a message storm and in appended data. But, I am 
guessing that that is not likely.

On Sep 26, 2019, at 1:54 PM, J. Landman Gay via use-livecode 
<use-livecode@lists.runrev.com> wrote:

On 9/24/19 2:39 PM, Dar Scott Consulting via use-livecode wrote:
Sources of memory leaks are LC, LC scripts, OS, libraries, LCB and (I suppose) 
compilers. I don't think we can assume the problem is not in the user script. I 
have seen script memory leaks like these:
1. Leaving large data in script locals
...

Is 2.5MB considered large data? I'm having issues on my Pixel that I think may 
be memory-related.

--
Jacqueline Landman Gay         |     jac...@hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



--
Jacqueline Landman Gay         |     jac...@hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to