LC Garbage Collection?
ambassador at fourthworld.com
Fri Sep 27 15:59:35 EDT 2019
I think "large" is dependent on context.
I've used LSON files larger than 100 MB, but I don't know that I would
recommend that for all possible use cases.
The bug DB link in this post suggests that size of a given array isn't
necessarily a problem or not a problem, it all depends on what
specifically you need to do with it, and whether you are unable to do
what you want in your app's context.
Fourth World Systems
J. Landman Gay wrote:> 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 at 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.
More information about the use-livecode